From: Tal Zussman <tz2294@columbia.edu>
To: Kees Cook <kees@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Cc: Tal Zussman <tz2294@columbia.edu>
Subject: [PATCH] compiler_types: Remove unnecessary indirection in compiletime_assert()
Date: Sat, 07 Jun 2025 03:23:55 -0400 [thread overview]
Message-ID: <20250607-compiletime_assert-v1-1-a8991a9be729@columbia.edu> (raw)
compiletime_assert() is the only user of _compiletime_assert(), which
uses __compiletime_assert() directly with no modification to arguments.
Remove _compiletime_assert() and use __compiletime_assert() directly.
Signed-off-by: Tal Zussman <tz2294@columbia.edu>
---
include/linux/compiler_types.h | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/include/linux/compiler_types.h b/include/linux/compiler_types.h
index 2b77d12e07b2..60d4fc8a89e5 100644
--- a/include/linux/compiler_types.h
+++ b/include/linux/compiler_types.h
@@ -552,9 +552,6 @@ struct ftrace_likely_data {
# define __compiletime_assert(condition, msg, prefix, suffix) ((void)(condition))
#endif
-#define _compiletime_assert(condition, msg, prefix, suffix) \
- __compiletime_assert(condition, msg, prefix, suffix)
-
/**
* compiletime_assert - break build and emit msg if condition is false
* @condition: a compile-time constant condition to check
@@ -565,7 +562,7 @@ struct ftrace_likely_data {
* compiler has support to do so.
*/
#define compiletime_assert(condition, msg) \
- _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
+ __compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
#define compiletime_assert_atomic_type(t) \
compiletime_assert(__native_word(t), \
---
base-commit: bdc7f8c5adad50dad2ec762e317f8b212f5782ac
change-id: 20250607-compiletime_assert-13dc76f26a92
Best regards,
--
Tal Zussman <tz2294@columbia.edu>
reply other threads:[~2025-06-07 7:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250607-compiletime_assert-v1-1-a8991a9be729@columbia.edu \
--to=tz2294@columbia.edu \
--cc=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.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
all inboxes | Powered by JetHome®