From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in the final build
Date: Tue, 18 Aug 2026 16:49:28 -0700 [thread overview]
Message-ID: <aoTt9Mka8iDVZKIQ@jpoimboe> (raw)
In-Reply-To: <aoTGgoeZ_FormkL-@sirena.org.uk>
On Tue, Aug 18, 2026 at 09:54:26PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the tree, today's linux-next build
> (arm64 allyesconfig) failed like this:
>
> ld: error: unplaced orphan section `.init.note.gnu.property' from `./drivers/firmware/efi/libstub/efi-stub-entry.stub.o'
> ...
> ld: error: unplaced orphan section `.init.note.gnu.property' from `./drivers/firmware/efi/libstub/smbios.stub.o'
> make[3]: *** [/tmp/next/build/scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
>
> Presumably caused by commit
>
> c19ac4abbd696 (efi/libstub: Remove obsolete .note.gnu.property workaround)
>
> though I did not verify. I have ignored this for today.
Ah, that commit had an implicit dependency on the previous patch in the
series, which wasn't merged:
https://lore.kernel.org/0445b20df50894615ada70abb1e6238f33c78a2e.1786768375.git.jpoimboe@kernel.org
Ard, can you rebase and slip that one underneath?
--
Josh
next prev parent reply other threads:[~2026-08-18 23:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 20:54 linux-next: build failure in the final build Mark Brown
2026-08-18 23:49 ` Josh Poimboeuf [this message]
2026-08-19 8:09 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2026-07-13 17:48 Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47 ` Manuel Ebner
2026-07-17 14:35 ` Greg Kroah-Hartman
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-06 14:50 linux-next: build " Mark Brown
2026-07-06 14:52 ` Johannes Berg
2026-06-10 15:51 Mark Brown
2026-01-21 17:14 Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24 ` Mark Brown
2026-01-21 18:14 ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24 ` Miguel Ojeda
2026-01-22 11:20 ` Mark Brown
2026-01-22 0:42 ` Deborah Brouwer
2026-01-22 11:17 ` Mark Brown
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=aoTt9Mka8iDVZKIQ@jpoimboe \
--to=jpoimboe@kernel.org \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.