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]
Date:   Wed, 16 Aug 2017 21:38:19 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Rob Herring <robh@...nel.org>
Cc:     Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
        "arm@...nel.org" <arm@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Roger Quadros <rogerq@...com>,
        Tony Lindgren <tony@...mide.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        linux-omap <linux-omap@...r.kernel.org>
Subject: Re: [PATCH] memory: Convert to using %pOF instead of full_name

On Thu, Aug 10, 2017 at 12:22 AM, Rob Herring <robh@...nel.org> wrote:
> On Wed, Jul 19, 2017 at 12:47 AM, Alexandre Belloni
> <alexandre.belloni@...e-electrons.com> wrote:
>> On 18/07/2017 at 16:43:14 -0500, Rob Herring 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: Nicolas Ferre <nicolas.ferre@...rochip.com>
>>> Cc: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
>>> Cc: Roger Quadros <rogerq@...com>
>>> Cc: Tony Lindgren <tony@...mide.com>
>>> Cc: linux-arm-kernel@...ts.infradead.org
>>> Cc: linux-omap@...r.kernel.org
>> Acked-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
>
> This can go through subsystem tree. Who normally takes drivers/memory/
> changes? arm-soc?

I applied it to next/drivers in arm-soc with the two acks now. For some
reason the whitespace change in omap-gpmc.c did not apply though,
so I ended up hand-editing the patch to take that out.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ