[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+kCA8QvdfU97TDcprfR3XuGj2WWO_mwiUSNr3D+WbU7g@mail.gmail.com>
Date: Tue, 28 Nov 2017 07:26:13 -0600
From: Rob Herring <robh@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Michael Ellerman <mpe@...erman.id.au>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Frank Rowand <frowand.list@...il.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
David Laight <David.Laight@...lab.com>
Subject: Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name
On Tue, Nov 28, 2017 at 7:13 AM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> Hi Rob,
>
> On Mon, Aug 21, 2017 at 5:16 PM, Rob Herring <robh@...nel.org> wrote:
>> With dependencies on a statically allocated full path name converted to
>> use %pOF format specifier, we can store just the basename of node, and
>> the unflattening of the FDT can be simplified.
>>
>> This commit will affect the remaining users of full_name. After
>> analyzing these users, the remaining cases should only change some print
>> messages. The main users of full_name are providing a name for struct
>> resource. The resource names shouldn't be important other than providing
>> /proc/iomem names.
>
> I guess the plan is to get rid in a subsequent step of all calls to kbasename()
> on a full name, which is now futile?
No. Sparc (PDT) is still the full path and I don't plan to change that.
Rob
Powered by blists - more mailing lists