linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Heiko Carstens <hca@linux.ibm.com>
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 09:42:28 +1000	[thread overview]
Message-ID: <20230828094228.2381967f@canb.auug.org.au> (raw)
In-Reply-To: <20230827203401.5559-B-hca@linux.ibm.com>

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

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.
-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2023-08-27 23:43 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 [this message]
2023-08-28  1:10     ` Stephen Rothwell
2023-08-28  8:31     ` Heiko Carstens
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=20230828094228.2381967f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).