From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Lai Jiangshan <laijs@linux.alibaba.com>,
stable@vger.kernel.org
Subject: Re: [PATCH V2] kvm: check tlbs_dirty directly
Date: Wed, 16 Dec 2020 10:46:07 +0100 [thread overview]
Message-ID: <X9nXX4h1mkcu0mw4@kroah.com> (raw)
In-Reply-To: <X9kEAh7z1rmlmyhZ@google.com>
On Tue, Dec 15, 2020 at 10:44:18AM -0800, Sean Christopherson wrote:
> Note, you don't actually need to Cc stable@vger.kernel.org when sending the
> patch. If/when the patch is merged to Linus' tree, the stable tree maintainers,
> or more accurately their scripts, will automatically pick up the patch and apply
> it to the relevant stable trees.
>
> You'll probably be getting the following letter from Greg KH any time now :-)
Nope, this was fine, I don't mind seeing the patch before it hits
Linus's tree (or any tree) at all. It lets me know what to look out
for, nothing was done incorrectly here at all from what I can tell.
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-16 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 4:49 [PATCH] kvm: don't lose the higher 32 bits of tlbs_dirty Lai Jiangshan
2020-12-14 17:20 ` Sean Christopherson
2020-12-15 5:14 ` Lai Jiangshan
2020-12-15 10:32 ` Paolo Bonzini
2020-12-15 14:52 ` [PATCH V2] kvm: check tlbs_dirty directly Lai Jiangshan
2020-12-15 18:44 ` Sean Christopherson
2020-12-16 9:46 ` Greg KH [this message]
2020-12-16 16:37 ` Paolo Bonzini
2020-12-17 15:41 ` [PATCH V3] " Lai Jiangshan
2020-12-21 18:31 ` Paolo Bonzini
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=X9nXX4h1mkcu0mw4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®