From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v3 1/5] include: <linux/math64.h>: include header for __always_inline definition
Date: Thu, 18 Feb 2021 10:38:58 +0100 [thread overview]
Message-ID: <20210218093902.15354-1-a.fatoum@pengutronix.de> (raw)
The Linux <linux/math64.h> depends on __always_inline being defined
prior. Fix this at our side now to avoid a build failure when using
it to replace <asm-generic/div64.h> later on.
Fixes: f933da28cf3f ("include: <linux/math64.h>: sync with upstream")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v2 -> v3:
- no change
v1 -> v2:
- new patch
---
include/linux/math64.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/math64.h b/include/linux/math64.h
index e8b737e70e50..8537c0412d09 100644
--- a/include/linux/math64.h
+++ b/include/linux/math64.h
@@ -3,6 +3,7 @@
#define _LINUX_MATH64_H
#include <linux/types.h>
+#include <linux/compiler.h>
#include <asm-generic/div64.h>
#if BITS_PER_LONG == 64
--
2.29.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2021-02-18 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 9:38 Ahmad Fatoum [this message]
2021-02-18 9:38 ` [PATCH v3 2/5] treewide: include <linux/math64.h> wrapper instead of <asm-generic/div64.h> Ahmad Fatoum
2021-02-18 9:39 ` [PATCH v3 3/5] include: asm-generic: don't do 64-bit soft division on 64-bit platforms Ahmad Fatoum
2021-02-18 9:39 ` [PATCH v3 4/5] lib: remove duplicate __div64_32 Ahmad Fatoum
2021-02-18 9:39 ` [PATCH v3 5/5] drivers: replaces references to <asm-generic/*.h> Ahmad Fatoum
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=20210218093902.15354-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