public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 6d501c05583a4efa513ff4b04a48ef41d5e8170e
Date: Sun, 18 Feb 2024 10:41:30 +0000	[thread overview]
Message-ID: <4Td2K66cchz2xlw@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2817 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, master has been updated
       via  6d501c05583a4efa513ff4b04a48ef41d5e8170e (commit)
      from  06a6788e51a863097fc2c6946767e8bf1b144e2f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6d501c05583a4efa513ff4b04a48ef41d5e8170e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Feb 18 11:38:29 2024 +0100

    cpufrequtils: hide output on disabled cores.
    
    We disable cores if the are affected by some cpu vulnerabilities
    this cores report errors if you try to change the settings.
    So only print the output for core0 and hide it for all cores.
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/cpufrequtils                 | 4 ++--
 src/initscripts/packages/cpufreq | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/lfs/cpufrequtils b/lfs/cpufrequtils
index 4bd5d0e51..8db0e6750 100644
--- a/lfs/cpufrequtils
+++ b/lfs/cpufrequtils
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2021  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2024  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = cpufrequtils
-PAK_VER    = 13
+PAK_VER    = 14
 
 DEPS       =
 
diff --git a/src/initscripts/packages/cpufreq b/src/initscripts/packages/cpufreq
index f133f3488..303eaf4bf 100644
--- a/src/initscripts/packages/cpufreq
+++ b/src/initscripts/packages/cpufreq
@@ -62,7 +62,7 @@ case "${1}" in
 			# Set the governor to ondemand for all cpus
 			for i in `seq 0 $CPUCOUNT`;
 			do
-				cpufreq-set -c $i -g $GOV
+				cpufreq-set -c $i -g $GOV > /dev/null
 			done
 			echo_ok;
 		else


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2024-02-18 10:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4Td2K66cchz2xlw@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox