From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Cc: Rouven Czerwinski <r.czerwinski@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/2] lib: fdt: define INT32_MAX for in-barebox use
Date: Tue, 1 Oct 2019 08:28:52 +0200 [thread overview]
Message-ID: <20191001062853.1256-2-ahmad@a3f.at> (raw)
In-Reply-To: <20191001062853.1256-1-ahmad@a3f.at>
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
The upcoming v1.5.1 version of libfdt adds a dependency on the C99
INT32_MAX symbol.
This is ok for use in the host tool, but libfdt can also be embedded
into barebox, where it would fail as we don't define this anywhere.
Fix this by providing an appropriate definition.
Reported-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
include/linux/libfdt_env.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/libfdt_env.h b/include/linux/libfdt_env.h
index edb0f0c30904..bac4670d6d7e 100644
--- a/include/linux/libfdt_env.h
+++ b/include/linux/libfdt_env.h
@@ -16,4 +16,6 @@ typedef __be64 fdt64_t;
#define fdt64_to_cpu(x) be64_to_cpu(x)
#define cpu_to_fdt64(x) cpu_to_be64(x)
+#define INT32_MAX 2147483647
+
#endif /* LIBFDT_ENV_H */
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent 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 [PATCH 0/2] dtc: fix breakage of in-barebox libfdt Ahmad Fatoum
2019-10-01 6:28 ` Ahmad Fatoum [this message]
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-2-ahmad@a3f.at \
--to=ahmad@a3f.at \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=r.czerwinski@pengutronix.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