From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Lai Jiangshan <laijs@linux.alibaba.com>,
stable@vger.kernel.org
Subject: Re: [PATCH V2] kvm: check tlbs_dirty directly
Date: Wed, 16 Dec 2020 17:37:51 +0100 [thread overview]
Message-ID: <37657f78-654e-ff81-e1c4-6ec31d6b99cf@redhat.com> (raw)
In-Reply-To: <X9kEAh7z1rmlmyhZ@google.com>
On 15/12/20 19:44, Sean Christopherson wrote:
> Note, you don't actually need to Ccstable@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:-)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>
As far as I know, as long as he sees LKML or something else in Cc he
assumes it's an indication _for the maintainer_. Don't underestimate
the power of Greg's mailing list filters. :)
Paolo
next prev parent reply other threads:[~2020-12-16 16:39 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
2020-12-16 16:37 ` Paolo Bonzini [this message]
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=37657f78-654e-ff81-e1c4-6ec31d6b99cf@redhat.com \
--to=pbonzini@redhat.com \
--cc=jiangshanlai@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome