From: Masahiro Yamada <masahiroy@kernel.org>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/3] libfdt: make lib/libfdt/ contain only wrappers
Date: Thu, 16 Apr 2020 18:30:15 +0900 [thread overview]
Message-ID: <20200416093018.561400-1-masahiroy@kernel.org> (raw)
Linux DT community follows the strict rule that they never locally
modify libfdt. In Linux, lib/fdt_*.c are wrapper files to
scripts/dtc/libfdt/fdt_*.c and scripts/dtc/ is synced with upstream
DTC by running scripts/dtc/update-dtc-source.sh
The local code in Linux is separated in drivers/of/.
On the other hand, U-Boot originally had own copies in lib/libfdt/,
and people locally modified them. The code diverged, and made it difficult
to re-sync with upstream.
In 2018, I worked on migrating them to wrapper files, just like Linux does.
50a327ded68b7e675389ad284ea3f8c62e683bda
87be1e9fb4dcc130e90d497cc5ce49c715efc6c2
26e961c8cfdff00c5c9389d301d9a2eb10eb844c
This series completes this work.
1/3 migrates fdt_ro.c to a wrapper.
Two years ago, it diverged from the upstream, and gave up resync.
Now, I do not see essential diff.
2/3 and 3/3 separate fdt_region out of the upstream code.
I am resending them after two years since the previous rejection.
It was unfortuate that they were rejected based on the assumption
that is unlikely to happen. They should be re-evaluated.
Masahiro Yamada (3):
libfdt: migrate fdt_ro.c to a wrapper of scripts/dtc/libfdt/fdt_ro.c
fdt_region: move fdt_region.c to common/ from lib/libfdt/
libfdt: split fdt_region declarations out to <fdt_region.h>
common/Makefile | 1 +
{lib/libfdt => common}/fdt_region.c | 1 +
common/image-fit-sig.c | 1 +
include/fdt_region.h | 304 +++++++++
include/linux/libfdt.h | 299 ---------
lib/libfdt/Makefile | 9 +-
lib/libfdt/fdt_ro.c | 925 +---------------------------
tools/Makefile | 13 +-
tools/fdtgrep.c | 1 +
tools/image-host.c | 1 +
tools/libfdt/fdt_ro.c | 2 +
11 files changed, 317 insertions(+), 1240 deletions(-)
rename {lib/libfdt => common}/fdt_region.c (99%)
create mode 100644 include/fdt_region.h
create mode 100644 tools/libfdt/fdt_ro.c
--
2.25.1
next reply other threads:[~2020-04-16 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 9:30 Masahiro Yamada [this message]
2020-04-16 9:30 ` [PATCH v2 1/3] libfdt: migrate fdt_ro.c to a wrapper of scripts/dtc/libfdt/fdt_ro.c Masahiro Yamada
2020-04-27 3:07 ` sjg at google.com
2020-04-16 9:30 ` [PATCH v2 2/3] fdt_region: move fdt_region.c to common/ from lib/libfdt/ Masahiro Yamada
2020-04-27 3:07 ` sjg at google.com
2020-04-16 9:30 ` [PATCH v2 3/3] libfdt: split fdt_region declarations out to <fdt_region.h> Masahiro Yamada
2020-04-27 3:07 ` sjg at google.com
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=20200416093018.561400-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=u-boot@lists.denx.de \
/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