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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gmkAS-A2eT5VUyuBMD9+FfsM0HL-HPeUYUV24_oMTvVw@mail.gmail.com>
Date:   Wed, 19 Jun 2019 14:28:08 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Rafael Wysocki <rjw@...ysocki.net>,
        Linux PM <linux-pm@...r.kernel.org>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/6] cpufreq: Use has_target() instead of !setpolicy

On Wed, Jun 19, 2019 at 1:36 PM Viresh Kumar <viresh.kumar@...aro.org> wrote:
>
> For code consistency, use has_target() instead of !setpolicy everywhere,
> as it is already done at several places.

That's OK

> Maybe we should also use !has_target() for setpolicy case to use only one expression
> for this differentiation.

But I'm not sure what you mean here?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ