From: Catalin Marinas <catalin.marinas@arm.com>
To: Arnd Bergmann <arnd@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Will Deacon <will@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
Boqun Feng <boqun.feng@gmail.com>,
clang-built-linux@googlegroups.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: make atomic helpers __always_inline
Date: Wed, 13 Jan 2021 16:06:35 +0000 [thread overview]
Message-ID: <161055398865.21762.4907792828255955851.b4-ty@arm.com> (raw)
In-Reply-To: <20210108092024.4034860-1-arnd@kernel.org>
On Fri, 8 Jan 2021 10:19:56 +0100, Arnd Bergmann wrote:
> With UBSAN enabled and building with clang, there are occasionally
> warnings like
>
> WARNING: modpost: vmlinux.o(.text+0xc533ec): Section mismatch in reference from the function arch_atomic64_or() to the variable .init.data:numa_nodes_parsed
> The function arch_atomic64_or() references
> the variable __initdata numa_nodes_parsed.
> This is often because arch_atomic64_or lacks a __initdata
> annotation or the annotation of numa_nodes_parsed is wrong.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: make atomic helpers __always_inline
https://git.kernel.org/arm64/c/c35a824c3183
--
Catalin
prev parent reply other threads:[~2021-01-13 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 9:19 [PATCH] arm64: make atomic helpers __always_inline Arnd Bergmann
2021-01-08 9:32 ` Will Deacon
2021-01-08 10:26 ` Arnd Bergmann
2021-01-08 18:50 ` Will Deacon
2021-01-08 20:04 ` Arnd Bergmann
2021-01-08 21:23 ` Nick Desaulniers
2021-01-08 20:39 ` Peter Zijlstra
2021-01-12 10:23 ` Mark Rutland
2021-01-13 13:44 ` Will Deacon
2021-01-13 16:06 ` Catalin Marinas [this message]
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=161055398865.21762.4907792828255955851.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).