public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: bad rebase of the kvms390 tree
Date: Tue, 13 Jun 2023 09:11:32 +0200	[thread overview]
Message-ID: <8701bac9-e604-40cc-74db-18b0ab1e7490@linux.ibm.com> (raw)
In-Reply-To: <20230613092726.0383cb94@canb.auug.org.au>

On 6/13/23 01:27, Stephen Rothwell wrote:
> Hi all,
> 
> The kvms390 tree has been rebased onto Linus' tree incorrectly - it
> includes duplicates of 3 commits from Linus' tree.
> 
> Please fix this up.
> 

@Claudio:
Not sure how you managed to do that.
Please have a look.

      reply	other threads:[~2023-06-13  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 23:27 linux-next: bad rebase of the kvms390 tree Stephen Rothwell
2023-06-13  7:11 ` Janosch Frank [this message]

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=8701bac9-e604-40cc-74db-18b0ab1e7490@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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