lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1598322.M8zmuJxMQN@vostro.rjw.lan>
Date:   Thu, 24 Nov 2016 02:17:30 +0100
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Stratos Karafotis <stratosk@...aphore.gr>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] cpufreq: conservative: Fix comment explaining frequency updates

On Thursday, November 17, 2016 09:10:59 AM Viresh Kumar wrote:
> On 16-11-16, 21:27, Stratos Karafotis wrote:
> > The original comment about the frequency increase to maximum is wrong.
> > 
> > Both increase and decrease happen at steps.
> > 
> > Signed-off-by: Stratos Karafotis <stratosk@...aphore.gr>
> > ---
> >  -> v2
> > Remove a trailing space
> > 
> >  drivers/cpufreq/cpufreq_conservative.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/cpufreq/cpufreq_conservative.c b/drivers/cpufreq/cpufreq_conservative.c
> > index a48b724..7522ec6 100644
> > --- a/drivers/cpufreq/cpufreq_conservative.c
> > +++ b/drivers/cpufreq/cpufreq_conservative.c
> > @@ -55,8 +55,8 @@ static inline unsigned int get_freq_step(struct cs_dbs_tuners *cs_tuners,
> >   * sampling_down_factor, we check, if current idle time is more than 80%
> >   * (default), then we try to decrease frequency
> >   *
> > - * Any frequency increase takes it to the maximum frequency. Frequency reduction
> > - * happens at minimum steps of 5% (default) of maximum frequency
> > + * Frequency updates happen at minimum steps of 5% (default) of maximum
> > + * frequency
> >   */
> >  static unsigned int cs_dbs_update(struct cpufreq_policy *policy)
> >  {
> 
> Acked-by: Viresh Kumar <viresh.kumar@...aro.org>

Applied.

Thanks,
Rafael

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ