From: Dan Carpenter <dan.carpenter@linaro.org>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Miguel Ojeda <ojeda@kernel.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] compiler.h: Add missing include statement for build_bug.h
Date: Thu, 14 Nov 2024 13:40:23 +0300 [thread overview]
Message-ID: <a2ed9ec0-4909-44bf-be11-21a22789e1d1@stanley.mountain> (raw)
In-Reply-To: <20241114101402.156397-2-philipp.reisner@linbit.com>
On Thu, Nov 14, 2024 at 11:14:02AM +0100, Philipp Reisner wrote:
> compiler.h defines __must_be_array() and __must_be_cstr() and both
> expand to BUILD_BUG_ON_ZERO(). build_bug.h defines BUILD_BUG_ON_ZERO().
> So far compiler.h lacks to include build_bug.h.
>
> Fix compiler.h by including build_bug.h. With that compiler.h and
> build_bug.h depend on each other.
>
> Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
> ---
Fixes: ec0bbef66f86 ("Compiler Attributes: homogenize __must_be_array")
What actually breaks? This commit is six years old. It's weird that we're only
seeing build breakage now. Or did you just notice this while reviewing the
code?
regards,
dan carpenter
> include/linux/compiler.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/compiler.h b/include/linux/compiler.h
> index 4d4e23b6e3e7..2d75e4892316 100644
> --- a/include/linux/compiler.h
> +++ b/include/linux/compiler.h
> @@ -3,6 +3,7 @@
> #define __LINUX_COMPILER_H
>
> #include <linux/compiler_types.h>
> +#include <linux/build_bug.h> /* for BUILD_BUG_ON_ZERO() */
>
> #ifndef __ASSEMBLY__
>
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-11-14 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 10:14 [PATCH 0/1] Add missing include in compiler.h Philipp Reisner
2024-11-14 10:14 ` [PATCH 1/1] compiler.h: Add missing include statement for build_bug.h Philipp Reisner
2024-11-14 10:40 ` Dan Carpenter [this message]
2024-11-14 11:01 ` Philipp Reisner
2024-11-14 11:05 ` Dan Carpenter
2024-11-14 17:42 ` Linus Torvalds
2024-11-14 18:28 ` Linus Torvalds
2024-11-14 18:40 ` Linus Torvalds
2024-11-15 20:46 ` [PATCH] compiler.h: Fix undefined BUILD_BUG_ON_ZERO() Philipp Reisner
2024-11-15 20:48 ` Kees Cook
2024-11-15 21:58 ` Linus Torvalds
2024-11-15 21:57 ` Linus Torvalds
2024-11-17 5:26 ` Kees Cook
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=a2ed9ec0-4909-44bf-be11-21a22789e1d1@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=ojeda@kernel.org \
--cc=philipp.reisner@linbit.com \
/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®