public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Sumanth Korikkar <sumanthk@linux.ibm.com>
Subject: linux-next: manual merge of the s390 tree with the kbuild tree
Date: Tue, 1 Apr 2025 11:31:09 +1100	[thread overview]
Message-ID: <20250401113109.2c8cb2b2@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi all,

Today's linux-next merge of the s390 tree got a conflict in:

  arch/s390/Makefile

between commit:

  9b400d17259b ("kbuild: Introduce Kconfig symbol for linking vmlinux with relocations")

from the kbuild tree and commit:

  991a20173a1f ("s390: Fix linker error when -no-pie option is unavailable")

from the s390 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.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/s390/Makefile
index d5f4be440879,fd3b70d9aab1..000000000000
--- a/arch/s390/Makefile
+++ b/arch/s390/Makefile
@@@ -15,7 -15,7 +15,7 @@@ KBUILD_CFLAGS_MODULE += -fPI
  KBUILD_AFLAGS	+= -m64
  KBUILD_CFLAGS	+= -m64
  KBUILD_CFLAGS	+= -fPIC
- LDFLAGS_vmlinux	:= -no-pie
 -LDFLAGS_vmlinux	:= $(call ld-option,-no-pie) --emit-relocs --discard-none
++LDFLAGS_vmlinux	:= $(call ld-option,-no-pie)
  extra_tools	:= relocs
  aflags_dwarf	:= -Wa,-gdwarf-2
  KBUILD_AFLAGS_DECOMPRESSOR := $(CLANG_FLAGS) -m64 -D__ASSEMBLY__

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-04-01  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  0:31 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-07 23:57 linux-next: manual merge of the s390 tree with the kbuild tree Stephen Rothwell
2024-05-08 13:18 ` Heiko Carstens
2017-03-30 23:54 Stephen Rothwell
2017-03-27 23:37 Stephen Rothwell

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=20250401113109.2c8cb2b2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ardb@kernel.org \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=sumanthk@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox