From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vipin Sharma <vipinsh@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the kvm-x86 tree
Date: Wed, 8 Feb 2023 14:41:31 +0000 [thread overview]
Message-ID: <Y+O0mypSEC58zYPD@google.com> (raw)
In-Reply-To: <20230208153847.5c89b497@canb.auug.org.au>
On Wed, Feb 08, 2023, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a `different
> commit (but the same patch):
>
> 4dfd8e37fa0f ("KVM: selftests: Make reclaim_period_ms input always be positive")
>
> This is commit
>
> c2c46b10d526 ("KVM: selftests: Make reclaim_period_ms input always be positive")
>
> in Linus' tree.
My bad, dropped it from kvm-x86.
Thanks!
prev parent reply other threads:[~2023-02-08 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 4:38 linux-next: duplicate patch in the kvm-x86 tree Stephen Rothwell
2023-02-08 14:41 ` 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=Y+O0mypSEC58zYPD@google.com \
--to=seanjc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=vipinsh@google.com \
/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).