From: Nathan Chancellor <nathan@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Nicolas Schier <nsc@kernel.org>,
Alexey Gladkov <legion@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Kees Cook <kees@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] kbuild: keep .modinfo when vmlinux is linked with --gc-sections
Date: Mon, 28 Sep 2026 13:56:28 +0200 [thread overview]
Message-ID: <20260928115628.GA964114@ax162> (raw)
In-Reply-To: <arpLoeLVATRCXm5E@gremlin>
On Mon, Sep 28, 2026 at 12:15:46PM +0100, Lorenzo Stoakes (ARM) wrote:
> Nathan - do you want me to fold this into the 1st patch of my series on respin
> or fine to treat separately?
Let's keep it separate since it is an existing issue and might want
to be backported in its own right.
I applied a subset of your series to kbuild-next-speedups to begin
exposing the "ready to go" (IMO at least) bits to -next (good thing
since it found this). You should be able to rebase on that for
subsequent versions, although maybe we still want to include those
changes for
others to continue to review but *shrug*. If there are follow up review
comments, just send delta patches and I will decide if I want to keep
them separate or squash them.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-09-28 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 16:12 Sasha Levin
2026-09-28 11:15 ` Lorenzo Stoakes (ARM)
2026-09-28 11:56 ` Nathan Chancellor [this message]
2026-09-28 12:16 ` Lorenzo Stoakes (ARM)
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=20260928115628.GA964114@ax162 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=legion@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=nsc@kernel.org \
--cc=sashal@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®