From: Michael Ellerman <mpe@ellerman•id.au>
To: Rob Herring <robh@kernel•org>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger•kernel.org>,
"devicetree\@vger.kernel.org" <devicetree@vger•kernel.org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Anatolij Gustschin <agust@denx•de>, Scott Wood <oss@buserror•net>,
Kumar Gala <galak@kernel•crashing.org>,
Arnd Bergmann <arnd@arndb•de>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH] powerpc: Convert to using %pOF instead of full_name
Date: Thu, 20 Jul 2017 13:34:12 +1000 [thread overview]
Message-ID: <87wp73hjd7.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAL_Jsq+f04cbTxoJEz8DW+TnE+TTO++F6M5=kBkMJkbO-w211g@mail.gmail.com>
Rob Herring <robh@kernel•org> writes:
> On Wed, Jul 19, 2017 at 7:03 AM, Michael Ellerman <mpe@ellerman•id.au> wrote:
>> Rob Herring <robh@kernel•org> writes:
>>
>>> 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@kernel•org>
>>> Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
>>> Cc: Paul Mackerras <paulus@samba•org>
>>> Cc: Michael Ellerman <mpe@ellerman•id.au>
>>> Cc: Anatolij Gustschin <agust@denx•de>
>>> Cc: Scott Wood <oss@buserror•net>
>>> Cc: Kumar Gala <galak@kernel•crashing.org>
>>> Cc: Arnd Bergmann <arnd@arndb•de>
>>> Cc: linuxppc-dev@lists•ozlabs.org
>>> ---
>> ...
>>> 79 files changed, 464 insertions(+), 490 deletions(-)
>>
>> Is the plan that I'll merge this for 4.14 ?
>
> Yes, hence why it's not a series and sent to you.
OK thanks. That was a bit too subtle for me :)
cheers
next prev parent reply other threads:[~2017-07-20 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:42 [PATCH] powerpc: Convert to using %pOF instead of full_name Rob Herring
2017-07-19 12:03 ` Michael Ellerman
2017-07-19 15:37 ` Rob Herring
2017-07-20 3:34 ` Michael Ellerman [this message]
2017-07-19 19:44 ` Tyrel Datwyler
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=87wp73hjd7.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=agust@denx$(echo .)de \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oss@buserror$(echo .)net \
--cc=paulus@samba$(echo .)org \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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