linux-kernel - Re: [PATCH] cpuidle: Convert to using %pOF instead of full

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]

Date:   Wed, 23 Aug 2017 15:49:00 -0500
From:   Rob Herring <robh@...nel.org>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     Rob Herring <robh@...nel.org>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: [PATCH] cpuidle: Convert to using %pOF instead of full_name

On Wed, Aug 23, 2017 at 3:34 PM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring <robh@...nel.org> wrote:
>> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring <robh@...nel.org> wrote:
>>> Now that we have a custom printf format specifier, convert users of
>>> full_name to use %pOF instead. This is preparation to remove storing
>>> of the full path string for each node.
>>>
>>> Signed-off-by: Rob Herring <robh@...nel.org>
>>> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>
>>> Cc: Daniel Lezcano <daniel.lezcano@...aro.org>
>>> Cc: linux-pm@...r.kernel.org
>>> ---
>>>  drivers/cpuidle/dt_idle_states.c | 20 ++++++++++----------
>>>  1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> Rafael, Ping. Please apply this one and 2 others for cpufreq and
>> PM-domains which haven't been applied yet.
>
> I thought that these would go in through the DT tree.
>
> I'll try to find them, but next time please make it clear how you want
> to route things.

Sorry, I thought addressed TO you and not in a series was enough to imply that.

Rob