From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] of: Convert to using %pOF instead of full_name
Date: Wed, 14 Jun 2017 13:58:34 -0700 [thread overview]
Message-ID: <1497473914.18751.72.camel@perches.com> (raw)
In-Reply-To: <20170614203025.7581-5-robh@kernel.org>
On Wed, 2017-06-14 at 15:30 -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.
Well, a full_name removal makes my reply in 2/4 less sensible.
Maybe 2/4 should say that full_name is going away.
prev parent reply other threads:[~2017-06-14 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 20:30 [PATCH 0/4] DT printf format specifiers Rob Herring
2017-06-14 20:30 ` [PATCH 1/4] of: use kbasename instead of open coding Rob Herring
2017-06-17 17:30 ` Andy Shevchenko
2017-06-14 20:30 ` [PATCH 2/4] of: find_node_by_full_name rewrite to compare each level Rob Herring
2017-06-14 20:30 ` [PATCH 3/4] of: Custom printk format specifier for device node Rob Herring
2017-06-14 20:56 ` Joe Perches
2017-06-15 12:30 ` Rob Herring
2017-06-15 16:51 ` Joe Perches
2017-06-15 21:26 ` Rob Herring
2017-06-15 21:50 ` Joe Perches
2017-06-22 20:44 ` [PATCH v2] vsprintf: Add %p extension "%pOF" for device tree Rob Herring
2017-06-22 22:44 ` Randy Dunlap
2017-06-23 14:08 ` Rob Herring
2017-06-23 3:01 ` Joe Perches
2017-06-23 14:13 ` Rob Herring
2017-06-23 17:30 ` [PATCH v3] " Rob Herring
2017-06-23 17:38 ` Joe Perches
2017-06-14 20:30 ` [PATCH 4/4] of: Convert to using %pOF instead of full_name Rob Herring
2017-06-14 20:58 ` Joe Perches [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=1497473914.18751.72.camel@perches.com \
--to=joe@perches.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh@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
Powered by JetHome