From: Rob Herring <robh@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Joe Perches <joe@perches.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] DT printf format specifiers
Date: Wed, 14 Jun 2017 15:30:21 -0500 [thread overview]
Message-ID: <20170614203025.7581-1-robh@kernel.org> (raw)
This resurrects an old patch[1] from Pantelis adding printf format
specifiers for DT nodes. The previous versions didn't get applied after
debate about the what character(s) to use. Grant suggested %pO for
base kobject and %pOF for struct device_node. Everyone agreed, but no
new version was posted.
I ended up re-writing the core implementation to be more inline with how
other format specifiers are written which allowed removing #define code
fragments. The other 3 patches convert the core DT code to use %pOF and
prepare for changing device_node.full_name to stop storing the full path
for every node.
My plan is to merge this series for v4.13 and post follow-up patches to
convert all arches and subsystems to %pOF for v4.14. The full series is
available here[2]. I tested this on QEMU running the DT unittests.
Rob
[1] https://patchwork.kernel.org/patch/6127521/
[2] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git dt-printf
Pantelis Antoniou (1):
of: Custom printk format specifier for device node
Rob Herring (3):
of: use kbasename instead of open coding
of: find_node_by_full_name rewrite to compare each level
of: Convert to using %pOF instead of full_name
Documentation/printk-formats.txt | 31 +++++++++
drivers/of/address.c | 21 +++---
drivers/of/base.c | 76 ++++++++++++----------
drivers/of/device.c | 2 +-
drivers/of/dynamic.c | 33 +++++-----
drivers/of/irq.c | 10 +--
drivers/of/of_mdio.c | 10 +--
drivers/of/of_pci.c | 29 ++++-----
drivers/of/of_private.h | 3 +
drivers/of/overlay.c | 21 +++---
drivers/of/platform.c | 34 +++++-----
drivers/of/resolver.c | 34 ++--------
drivers/of/unittest.c | 66 +++++++++++--------
lib/vsprintf.c | 135 ++++++++++++++++++++++++++++++++++++++-
scripts/checkpatch.pl | 2 +-
15 files changed, 331 insertions(+), 176 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-14 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 20:30 Rob Herring [this message]
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
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=20170614203025.7581-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
/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).