From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
KBuild Mailing List <linux-kbuild@vger.kernel.org>
Cc: Kees Cook <kees@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Magnus Lindholm <linmag7@gmail.com>,
Matt Turner <mattst88@gmail.com>
Subject: linux-next: manual merge of the kbuild-current tree with the origin tree
Date: Wed, 21 Oct 2026 12:01:24 +0100 [thread overview]
Message-ID: <atibhAMcgKle37-g@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Hi all,
Today's linux-next merge of the kbuild-current tree got a conflict in:
arch/alpha/boot/Makefile
between commit:
c437950dceb88 ("alpha: add self-extracting compressed kernel boot stub")
from the origin tree and commit:
0d4d70da348b0 ("kbuild: Mark the gzip recipes as recursive")
from the kbuild-current tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc arch/alpha/boot/Makefile
index 7c2a41c1e2a06,b050753e90157..0000000000000
--- a/arch/alpha/boot/Makefile
+++ b/arch/alpha/boot/Makefile
@@@ -39,14 -38,9 +39,14 @@@ ifdef INITR
cat $(INITRD) >> $@
endif
-# Compressed kernel image
-$(obj)/vmlinux.gz: $(obj)/vmlinux FORCE
- +$(call if_changed,gzip)
+# Self-extracting compressed kernel image: a small ELF stub (see
+# compressed/) with the real vmlinux linked in compressed, which aboot
+# loads and enters like a plain vmlinux.
+$(obj)/compressed/vmlinux: vmlinux FORCE
+ $(Q)$(MAKE) $(build)=$(obj)/compressed $@
+
+$(obj)/vmlinuz: $(obj)/compressed/vmlinux FORCE
- $(call if_changed,copy)
++ +$(call if_changed,copy)
@echo ' Kernel $@ is ready'
$(obj)/main.o: $(obj)/ksize.h
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-10-21 11:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=atibhAMcgKle37-g@sirena.co.uk \
--to=broonie@kernel.org \
--cc=kees@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=nathan@kernel.org \
--cc=nsc@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®