From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Subject: [PATCH 0/2] dtc: fix breakage of in-barebox libfdt
Date: Tue, 1 Oct 2019 08:28:51 +0200 [thread overview]
Message-ID: <20191001062853.1256-1-ahmad@a3f.at> (raw)
I missed that I have to test CONFIG_BOARD_ARM_GENERIC_DT as well when
updating dtc. Please apply the first commit before the
("scripts/dtc: Update to upstream version v1.5.1") commit, so it's not
intermittently broken.
Also attached is a fixup to the documentation that makes note of this.
Ahmad Fatoum (2):
lib: fdt: define INT32_MAX for in-barebox use
fixup! Documentation: document barebox device tree handling
Documentation/devicetree/index.rst | 17 ++++++++++-------
include/linux/libfdt_env.h | 2 ++
2 files changed, 12 insertions(+), 7 deletions(-)
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-10-01 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 6:28 Ahmad Fatoum [this message]
2019-10-01 6:28 ` [PATCH 1/2] lib: fdt: define INT32_MAX for in-barebox use Ahmad Fatoum
2019-10-01 6:28 ` [PATCH 2/2] fixup! Documentation: document barebox device tree handling Ahmad Fatoum
2019-10-02 6:48 ` [PATCH 0/2] dtc: fix breakage of in-barebox libfdt 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=20191001062853.1256-1-ahmad@a3f.at \
--to=ahmad@a3f.at \
--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