From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Nathan Chancellor <nathan@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: Wed, 30 Sep 2026 10:04:51 +0100 [thread overview]
Message-ID: <arzOxTQhvWwcqdDU@gremlin> (raw)
In-Reply-To: <20260929201402.GA3237201@ax162>
On Tue, Sep 29, 2026 at 10:14:02PM +0200, Nathan Chancellor wrote:
> On Mon, Sep 28, 2026 at 01:16:27PM +0100, Lorenzo Stoakes (ARM) wrote:
> > Ack, will rebase on that and send deltas from here on out on those.
> >
> > Easiest to keep things straight on my side would be to stop sending those
> > patches, I can list them in the cover letter with links to the originals
> > for any further review?
>
> Sure, that sounds totally reasonable to me.
Thanks!
>
> > As for what remains, is there anything else I need to do?
> >
> > I think timing this week is less than ideal with LPC next week so people
> > have less time to go through it but it does feel like things are
> > stabilising (despite the large changelog for v4 ;)
>
> Yeah, I have been spread quite thin between trying to keep the current
> ClangBuiltLinux continuous integration setup green, developing a new one
> due to changing constraints elsewhere, updating my own personal testing
> framework to be quicker for more efficient local testing (especially for
> stuff like this), and my Kbuild maintainer duties, in addition to some
> personal time off for my wife's birthday before Plumbers.
Yeah indeed, totally understood. And I hope you enjoy your time off :)
This cycle has been crazy (2x baseline for 2025 and it seems that way
across many subsystems), and the LPC timing is unfortunate, so I can fully
understand why people have had less time for this series.
(I also have a personal interest in clang working for the kernel also as
all my builds are clang-by-default now and have been for a while!)
>
> All that to say, I am not sure how much else I will want to take for 7.4
> at this point, as I would like to have the kbuild tree basically
> finalized by 7.3-rc7, which is the weekend right after Plumbers if my
> calendar is correct. I would like to study these patches to make sure I
> understand everything well and I don't think I will have the time to do
> that until after the 7.4 merge window opens.
Sure, fully understood!
Stripping the stuff you have queued up from the series (+ sending deltas if
needed) will make it easier to send the rest post-merge window anyway.
>
> > Thanks for all your help with this! Is much appreciated.
>
> Absolutely, thanks for engaging and trying to make Kbuild better :)
No worries :)
>
> --
> Cheers,
> Nathan
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-30 9:04 UTC|newest]
Thread overview: 6+ 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
2026-09-28 12:16 ` Lorenzo Stoakes (ARM)
2026-09-29 20:14 ` Nathan Chancellor
2026-09-30 9:04 ` Lorenzo Stoakes (ARM) [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=arzOxTQhvWwcqdDU@gremlin \
--to=ljs@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=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--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®