From: Frank Rowand <frowand.list@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Pantelis Antoniou <panto@antoniou-consulting.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] of: remove kbasename() from core
Date: Mon, 26 Feb 2018 11:42:16 -0800 [thread overview]
Message-ID: <48509f67-9e94-ebe6-746b-c1262ea143b0@gmail.com> (raw)
In-Reply-To: <CAMuHMdUj63OQnJWz=Q57dbc1XKOnq+_et5-E_4yQjTZt+c++GQ@mail.gmail.com>
On 02/26/18 01:03, Geert Uytterhoeven wrote:
> Hi Frank,
>
> On Mon, Feb 26, 2018 at 3:22 AM, <frowand.list@gmail.com> wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> Struct device_node full_name no longer includes the full path
>> name.
>
> Is this now also true on systems with real Open Firmware?
Thanks, good point. I can not remove the kbasename() calls.
Will re-spin, as a much smaller patch to deal with the
overlay issues.
-Frank
prev parent reply other threads:[~2018-02-26 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 2:22 [PATCH 0/6] of: remove kbasename() from core frowand.list
2018-02-26 2:22 ` [PATCH 1/6] of: unittest: clean up changeset test frowand.list
2018-02-26 2:22 ` [PATCH 2/6] of: remove kbasename(of->full_name) from overlay related code frowand.list
2018-02-26 2:22 ` [PATCH 3/6] of: remove kbasename(of->full_name) from base.c frowand.list
2018-02-26 2:22 ` [PATCH 4/6] of: remove kbasename(of->full_name) from kobj.c frowand.list
2018-02-26 2:22 ` [PATCH 5/6] of: remove kbasename(of->full_name) from of_reserved_mem.c frowand.list
2018-02-26 2:22 ` [PATCH 6/6] of: remove kbasename(of->full_name) from platform.c frowand.list
2018-02-26 9:03 ` [PATCH 0/6] of: remove kbasename() from core Geert Uytterhoeven
2018-02-26 19:42 ` Frank Rowand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48509f67-9e94-ebe6-746b-c1262ea143b0@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).