From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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-x86 tree
Date: Thu, 7 Sep 2023 18:18:56 -0700 [thread overview]
Message-ID: <ZPp2gIw5AGMcv4IV@google.com> (raw)
In-Reply-To: <20230908101819.65e8994c@canb.auug.org.au>
On Fri, Sep 08, 2023, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
I'll force push, Paolo squashed a minor fixup and I haven't updated.
next prev parent reply other threads:[~2023-09-08 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 0:18 linux-next: duplicate patches in the kvm-x86 tree Stephen Rothwell
2023-09-08 1:18 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 4:24 Stephen Rothwell
2024-07-19 3:44 Stephen Rothwell
2024-07-19 13:21 ` Sean Christopherson
2023-10-17 4:37 Stephen Rothwell
2023-10-17 16:34 ` Sean Christopherson
2023-01-24 1:55 Stephen Rothwell
2023-01-24 8:46 ` Marc Zyngier
2023-01-24 11:09 ` Paolo Bonzini
2023-01-24 16:15 ` Sean Christopherson
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=ZPp2gIw5AGMcv4IV@google.com \
--to=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.