From: Ard Biesheuvel <ardb@kernel.org>
To: Yann Sionneau <ysionneau@kalray.eu>
Cc: linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] Fix __kcrctab+* sections alignment
Date: Thu, 25 Aug 2022 14:12:15 +0200 [thread overview]
Message-ID: <CAMj1kXF8mZ_pK38T=dCU6Rewqq23pPM5HwnZHyx1cGgo0F7Mew@mail.gmail.com> (raw)
In-Reply-To: <31ce5305-a76b-13d7-ea55-afca82c46cf2@kalray.eu>
On Thu, 25 Aug 2022 at 14:10, Yann Sionneau <ysionneau@kalray.eu> wrote:
>
> Forwarding also the actual patch to linux-kbuild and linux-arch
>
> -------- Forwarded Message --------
> Subject: [RFC PATCH 1/1] Fix __kcrctab+* sections alignment
> Date: Wed, 17 Aug 2022 18:14:38 +0200
> From: Yann Sionneau <ysionneau@kalray.eu>
> To: linux-kernel@vger.kernel.org
> CC: Nicolas Schier <nicolas@fjasle.eu>, Masahiro Yamada
> <masahiroy@kernel.org>, Jules Maselbas <jmaselbas@kalray.eu>, Julian
> Vetter <jvetter@kalray.eu>, Yann Sionneau <ysionneau@kalray.eu>
>
>
>
What happened to the commit log?
> Signed-off-by: Yann Sionneau <ysionneau@kalray.eu>
> ---
> include/linux/export-internal.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/export-internal.h
> b/include/linux/export-internal.h
> index c2b1d4fd5987..d86bfbd7fa6d 100644
> --- a/include/linux/export-internal.h
> +++ b/include/linux/export-internal.h
> @@ -12,6 +12,6 @@
> /* __used is needed to keep __crc_* for LTO */
> #define SYMBOL_CRC(sym, crc, sec) \
> - u32 __section("___kcrctab" sec "+" #sym) __used __crc_##sym = crc
> + u32 __section("___kcrctab" sec "+" #sym) __used __aligned(4)
__aligned(4) is the default for u32 so this should not be needed.
> __crc_##sym = crc
> #endif /* __LINUX_EXPORT_INTERNAL_H__ */
>
> --
> 2.37.2
>
>
>
>
>
next prev parent reply other threads:[~2022-08-25 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220817161438.32039-2-ysionneau@kalray.eu>
2022-08-25 12:03 ` Fwd: [RFC PATCH 1/1] Fix __kcrctab+* sections alignment Yann Sionneau
2022-08-25 12:12 ` Ard Biesheuvel [this message]
2022-08-25 12:21 ` Yann Sionneau
2022-08-25 12:41 ` Ard Biesheuvel
2022-08-25 18:01 ` Geert Uytterhoeven
2022-08-26 10:17 ` Ard Biesheuvel
2022-08-28 14:05 ` Masahiro Yamada
2022-09-05 15:26 ` Yann Sionneau
2022-09-26 8:48 ` Yann Sionneau
2022-09-26 9:05 ` Masahiro Yamada
2022-09-26 9:11 ` Ard Biesheuvel
2022-09-26 9:05 ` Ard Biesheuvel
2022-08-28 13:41 ` Masahiro Yamada
2022-08-28 13:59 ` Masahiro Yamada
2022-09-05 13:56 ` Yann Sionneau
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='CAMj1kXF8mZ_pK38T=dCU6Rewqq23pPM5HwnZHyx1cGgo0F7Mew@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=ysionneau@kalray.eu \
/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).