From: Hauke Mehrtens <hauke@hauke-m.de>
To: backports@vger.kernel.org
Cc: johannes@sipsolutions.net, Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 03/11] backports: build_bug.h: Add static_assert()
Date: Thu, 3 Oct 2019 17:56:34 +0200 [thread overview]
Message-ID: <20191003155642.14909-4-hauke@hauke-m.de> (raw)
In-Reply-To: <20191003155642.14909-1-hauke@hauke-m.de>
Add static_assert() from upstream commit 6bab69c65013 ("build_bug.h: add
wrapper for _Static_assert") which is used by rtw88.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
backport/backport-include/linux/build_bug.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/backport/backport-include/linux/build_bug.h b/backport/backport-include/linux/build_bug.h
index 13ee5d6a..c883e525 100644
--- a/backport/backport-include/linux/build_bug.h
+++ b/backport/backport-include/linux/build_bug.h
@@ -7,4 +7,25 @@
#include <linux/bug.h>
#endif /* LINUX_VERSION_IS_GEQ(4,13,0) */
+#ifndef static_assert
+/**
+ * static_assert - check integer constant expression at build time
+ *
+ * static_assert() is a wrapper for the C11 _Static_assert, with a
+ * little macro magic to make the message optional (defaulting to the
+ * stringification of the tested expression).
+ *
+ * Contrary to BUILD_BUG_ON(), static_assert() can be used at global
+ * scope, but requires the expression to be an integer constant
+ * expression (i.e., it is not enough that __builtin_constant_p() is
+ * true for expr).
+ *
+ * Also note that BUILD_BUG_ON() fails the build if the condition is
+ * true, while static_assert() fails the build if the expression is
+ * false.
+ */
+#define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
+#define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
+#endif
+
#endif /* __BP_BUILD_BUG_H */
--
2.20.1
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2019-10-03 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 15:56 [PATCH 00/11] backports: Update to kernel 5.4-rc1 Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 01/11] backports: patches: refresh against " Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 02/11] backports: pci: include linux/pci-aspm.h Hauke Mehrtens
2019-10-03 15:56 ` Hauke Mehrtens [this message]
2019-10-03 15:56 ` [PATCH 04/11] backports: platform_device.h: Add devm_platform_ioremap_resource() Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 05/11] backports: skbuf.h: Add skb_frag_off() Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 06/11] backports: skbuff.h: Add skb_mac_offset() Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 07/11] backports: io.h: Add __ioread32_copy() Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 08/11] backports: io: Add writel_relaxed() Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 09/11] backports: dependencies: make ATH9K OWL depend on kernel 3.14 Hauke Mehrtens
2019-10-04 8:55 ` Johannes Berg
2019-10-04 19:34 ` Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 10/11] backports: lib-arc4: Do not build when activated in kernel Hauke Mehrtens
2019-10-03 15:56 ` [PATCH 11/11] backports: ckmake: limit load to number of CPUs Hauke Mehrtens
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=20191003155642.14909-4-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
/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;
as well as URLs for NNTP newsgroup(s).