From: Brian Norris <briannorris@chromium.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: linux-kernel@vger.kernel.org, Bill Wendling <morbo@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Justin Stitt <justinstitt@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
llvm@lists.linux.dev, Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v3 3/4] cpumask: Switch from inline to __always_inline
Date: Fri, 2 Aug 2024 14:19:48 -0700 [thread overview]
Message-ID: <Zq1NdFXhN3IoYm3M@google.com> (raw)
In-Reply-To: <20240719005127.2449328-3-briannorris@chromium.org>
On Thu, Jul 18, 2024 at 05:50:39PM -0700, Brian Norris wrote:
> On recent (v6.6+) builds with Clang (based on Clang 18.0.0) and certain
> configurations [0], I'm finding that (lack of) inlining decisions may
> lead to section mismatch warnings like the following:
>
> WARNING: modpost: vmlinux.o: section mismatch in reference:
> cpumask_andnot (section: .text) ->
> cpuhp_bringup_cpus_parallel.tmp_mask (section: .init.data) ERROR:
> modpost: Section mismatches detected.
...
Hi Yury,
I'm wondering if you've had a chance to look at this latest series. I
believe I refactored it the way you recommended.
Regards,
Brian
next prev parent reply other threads:[~2024-08-02 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 0:50 [PATCH v3 1/4] find: Switch from inline to __always_inline Brian Norris
2024-07-19 0:50 ` [PATCH v3 2/4] bitmap: " Brian Norris
2024-07-19 0:50 ` [PATCH v3 3/4] cpumask: " Brian Norris
2024-08-02 21:19 ` Brian Norris [this message]
2024-08-03 13:21 ` Yury Norov
2024-07-19 0:50 ` [PATCH v3 4/4] nodemask: " Brian Norris
2024-08-02 23:07 ` [PATCH v3 1/4] find: " Nathan Chancellor
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=Zq1NdFXhN3IoYm3M@google.com \
--to=briannorris@chromium.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=yury.norov@gmail.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