From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, nathan@kernel.org
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: new objtool warnings
Date: Wed, 5 Nov 2025 11:10:10 +0100 [thread overview]
Message-ID: <20251105101010.GA4068168@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251105100202.GZ4068168@noisy.programming.kicks-ass.net>
+ Nathan
On Wed, Nov 05, 2025 at 11:02:02AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 05, 2025 at 11:00:14AM +0100, Peter Zijlstra wrote:
> > On Wed, Nov 05, 2025 at 09:56:37AM +0100, Peter Zijlstra wrote:
> > > On Wed, Nov 05, 2025 at 02:30:27PM +1100, Stephen Rothwell wrote:
> > >
> > > > These objtool messages have returned today. No change in compiler.
> > >
> > > Yes, Ingo also reported them on IRC, let me go investigate!
> >
> > The below cures things, but I'm not quite sure why they show up now and
> > not before. Let me poke more.
>
> Also, someone wrecked the build system.
>
> vmlinux.o is no longer a valid build target, and the vmlinux target
> seems to build a ton of module stuff :/
next prev parent reply other threads:[~2025-11-05 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 0:15 linux-next: new objtool warnings Stephen Rothwell
2025-11-03 9:10 ` Peter Zijlstra
2025-11-03 9:32 ` Stephen Rothwell
2025-11-03 9:38 ` Peter Zijlstra
2025-11-05 3:30 ` Stephen Rothwell
2025-11-05 8:56 ` Peter Zijlstra
2025-11-05 10:00 ` Peter Zijlstra
2025-11-05 10:02 ` Peter Zijlstra
2025-11-05 10:10 ` Peter Zijlstra [this message]
2025-11-05 17:07 ` Nathan Chancellor
2025-11-05 19:16 ` Peter Zijlstra
2025-11-05 20:09 ` Nathan Chancellor
2025-11-06 11:48 ` Peter Zijlstra
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=20251105101010.GA4068168@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=sfr@canb.auug.org.au \
/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