From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the kvm tree
Date: Mon, 11 Dec 2023 09:49:38 -0800 [thread overview]
Message-ID: <ZXdLsg1tN4DfBBSy@google.com> (raw)
In-Reply-To: <20231211085956.25bedfe4@canb.auug.org.au>
On Mon, Dec 11, 2023, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 3b99d46a1170 ("KVM: selftests: Actually print out magic token in NX hugepages skip message")
> fc6543bb55d4 ("KVM: selftests: add -MP to CFLAGS")
>
> These are commits
>
> 4a073e813477 ("KVM: selftests: Actually print out magic token in NX hugepages skip message")
> 96f124015f82 ("KVM: selftests: add -MP to CFLAGS")
>
> in Linus' tree.
This is my bad, I used the wrong base for a selftests branch. My understanding
is that we're just going to eat the duplicate commits.
prev parent reply other threads:[~2023-12-11 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 21:59 linux-next: duplicate patches in the kvm tree Stephen Rothwell
2023-12-11 17:49 ` Sean Christopherson [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=ZXdLsg1tN4DfBBSy@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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