From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/3] commands: of_diff: support applying fixups on arbitrary device trees
Date: Thu, 8 Jun 2023 15:40:38 +0200 [thread overview]
Message-ID: <20230608134040.2123869-1-a.fatoum@pengutronix.de> (raw)
of_diff - + is quite useful to find what fixups barebox would apply to
its own device tree. But for some cases, like barebox-state or OP-TEE
reservations, the nodes that would be fixed up into the kernel device
tree already exist within the barebox device tree and wouldn't be shown
by of_diff - +. To make them visible, let's redefine +:
- Previously, it always meant the fixed up barebox DT
- Now, it means the other DT with fixups applied
That way, of_diff - + continues to work, but kernel DTs can now be
diffed against their fixed up version by doing:
of_diff /mnt/tftp/afa-oftree-myboard +
Ahmad Fatoum (3):
of: change superfluous of_fix_tree int return type to void
commands: of_diff: simplify error handling
commands: of_diff: support applying fixups on arbitrary device trees
commands/of_compatible.c | 7 ++---
commands/of_diff.c | 63 +++++++++++++++++++---------------------
commands/of_dump.c | 7 ++---
common/oftree.c | 10 ++-----
drivers/of/base.c | 3 ++
include/of.h | 2 +-
6 files changed, 40 insertions(+), 52 deletions(-)
--
2.39.2
next reply other threads:[~2023-06-08 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:40 Ahmad Fatoum [this message]
2023-06-08 13:40 ` [PATCH 1/3] of: change superfluous of_fix_tree int return type to void Ahmad Fatoum
2023-06-08 13:40 ` [PATCH 2/3] commands: of_diff: simplify error handling Ahmad Fatoum
2023-06-13 11:48 ` Johannes Zink
2023-06-08 13:40 ` [PATCH 3/3] commands: of_diff: support applying fixups on arbitrary device trees Ahmad Fatoum
2023-06-09 6:41 ` [PATCH 0/3] " Sascha Hauer
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=20230608134040.2123869-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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