From: Heiko Carstens <hca@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] s390 updates for 6.6 merge window
Date: Mon, 28 Aug 2023 10:31:50 +0200 [thread overview]
Message-ID: <20230828083150.19928-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20230828094228.2381967f@canb.auug.org.au>
On Mon, Aug 28, 2023 at 09:42:28AM +1000, Stephen Rothwell wrote:
> Hi Heiko,
>
> On Sun, 27 Aug 2023 22:34:01 +0200 Heiko Carstens <hca@linux.ibm.com> wrote:
> >
> > On Sun, Aug 27, 2023 at 10:31:00PM +0200, Heiko Carstens wrote:
> >
> > Maybe I'm doing something wrong, but below is the rather large diff
> > of the merge commit, using "git diff HEAD HEAD^@", where HEAD is the
> > merge commit.
>
> Something weird there. I just see the arch/s390/Kconfig part (I use
> git diff-tree <merge commit>). What did you merge?
>
> I can't see any commits affecting kernel/Kconfig.kexec in the s390
> branch in linux-next.
There is logical conflict between
commit 37002bc6b603 ("docs: move s390 under arch")
from the s390 tree:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux tags/s390-6.6-1
and
commit 89cde455915f ("kexec: consolidate kexec and crash options into kernel/Kconfig.kexec")
from Andrew's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-nonmm-stable
The commit in Andrew's tree introduces kernel/Kconfic.kexec and uses the
old location for Documentation (which is correct for Andrew's tree). So
when merging the s390 tree and Andrew's tree into Linus' tree that should
be fixed as well (btw.: this is not "fixed" in linux-next).
So I guess the size of the merge commit diff is simply a result of
kernel/Kconfig.exec not being present in both trees and being modified with
the merge, and therefore the complete file is part of the diff.
next prev parent reply other threads:[~2023-08-28 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 20:30 [GIT PULL] s390 updates for 6.6 merge window Heiko Carstens
2023-08-27 20:34 ` Heiko Carstens
2023-08-27 23:42 ` Stephen Rothwell
2023-08-28 1:10 ` Stephen Rothwell
2023-08-28 8:31 ` Heiko Carstens [this message]
2023-08-29 0:46 ` pr-tracker-bot
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=20230828083150.19928-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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