LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yanfei Xu <isyanfei.xu@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Yanfei Xu <yanfei.xu@bytedance.com>
Cc: harshpb@linux.ibm.com, zhaotianrui@loongson.cn,
	maobibo@loongson.cn, chenhuacai@kernel.org, maddy@linux.ibm.com,
	npiggin@gmail.com, sashiko-reviews@lists.linux.dev,
	seanjc@google.com, pbonzini@redhat.com, kvm@vger.kernel.org,
	stable@vger.kernel.org, loongarch@lists.linux.dev,
	linuxppc-dev@lists.ozlabs.org, caixiangfeng@bytedance.com,
	fangying.tommy@bytedance.com
Subject: Re: [v2 0/2] KVM: Validate irqchip index in routing entries
Date: Sun, 31 May 2026 22:36:27 +0800	[thread overview]
Message-ID: <5ee310d9-d432-400d-8506-751ee4a41fc6@gmail.com> (raw)
In-Reply-To: <2026053158-cussed-outweigh-6f0f@gregkh>


On 2026/5/31 22:15, Greg KH wrote:
>> -- 
>> 2.20.1
>>
> <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>

Thanks for pointing out the correct process. I saw
that PPC maintainer added "Cc: stable@vger.kernel.org"
on v1, so I mistakenly thought v2 should cc...

Thanks,
Yanfei



  reply	other threads:[~2026-05-31 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 13:53 [v2 0/2] KVM: Validate irqchip index in routing entries Yanfei Xu
2026-05-31 13:53 ` [v2 1/2] KVM: LoongArch: Validate irqchip index in irqfd routing Yanfei Xu
2026-06-07  4:41   ` Huacai Chen
2026-05-31 13:53 ` [v2 2/2] KVM: PPC: Validate irqchip index in MPIC routing Yanfei Xu
2026-05-31 14:15 ` [v2 0/2] KVM: Validate irqchip index in routing entries Greg KH
2026-05-31 14:36   ` Yanfei Xu [this message]
2026-05-31 15:25     ` Greg KH

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=5ee310d9-d432-400d-8506-751ee4a41fc6@gmail.com \
    --to=isyanfei.xu@gmail.com \
    --cc=caixiangfeng@bytedance.com \
    --cc=chenhuacai@kernel.org \
    --cc=fangying.tommy@bytedance.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harshpb@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maddy@linux.ibm.com \
    --cc=maobibo@loongson.cn \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=seanjc@google.com \
    --cc=stable@vger.kernel.org \
    --cc=yanfei.xu@bytedance.com \
    --cc=zhaotianrui@loongson.cn \
    /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