From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>, "Christopherson,,
Sean" <seanjc@google.com>
Cc: "Li, Xiaoyao" <xiaoyao.li@intel.com>,
"eesposit@redhat.com" <eesposit@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"pshier@google.com" <pshier@google.com>,
"bagasdotme@gmail.com" <bagasdotme@gmail.com>,
"jthoughton@google.com" <jthoughton@google.com>,
"Zeng, Guang" <guang.zeng@intel.com>,
"jmattson@google.com" <jmattson@google.com>,
"leobras@redhat.com" <leobras@redhat.com>,
"bgardon@google.com" <bgardon@google.com>,
"pgonda@google.com" <pgonda@google.com>,
"Liu, Jing2" <jing2.liu@intel.com>,
"amoorthy@google.com" <amoorthy@google.com>,
"nikunj@amd.com" <nikunj@amd.com>,
"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"mhal@rbox.co" <mhal@rbox.co>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"mizhang@google.com" <mizhang@google.com>,
"Shahar, Sagi" <sagis@google.com>,
"michael.roth@amd.com" <michael.roth@amd.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"aghulati@google.com" <aghulati@google.com>,
"ricarkol@google.com" <ricarkol@google.com>,
"bp@alien8.de" <bp@alien8.de>,
"flyingpenghao@gmail.com" <flyingpenghao@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"axelrasmussen@google.com" <axelrasmussen@google.com>,
"robert.hu@linux.intel.com" <robert.hu@linux.intel.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"vipinsh@google.com" <vipinsh@google.com>,
"ashish.kalra@amd.com" <ashish.kalra@amd.com>,
"Qiang, Chenyi" <chenyi.qiang@intel.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"dmatlack@google.com" <dmatlack@google.com>,
"aaronlewis@google.com" <aaronlewis@google.com>,
"Szmigiero, Maciej" <maciej.szmigiero@oracle.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"pdurrant@amazon.com" <pdurrant@amazon.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"yu.c.zhang@linux.intel.com" <yu.c.zhang@linux.intel.com>,
"junaids@google.com" <junaids@google.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"jiaxi.chen@linux.intel.com" <jiaxi.chen@linux.intel.com>,
"Li, Rongqing" <lirongqing@baidu.com>,
"gshan@redhat.com" <gshan@redhat.com>,
"like.xu.linux@gmail.com" <like.xu.linux@gmail.com>,
"babu.moger@amd.com" <babu.moger@amd.com>,
"Wang, Wei W" <wei.w.wang@intel.com>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
"houwenlong.hwl@antgroup.com" <houwenlong.hwl@antgroup.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Gao, Chao" <chao.gao@intel.com>
Subject: Re: [PATCH v3 2/2] Documentation/process: Add a maintainer handbook for KVM x86
Date: Wed, 12 Apr 2023 10:04:33 +0000 [thread overview]
Message-ID: <4e3706bd9dccc6cd00eab9c59e06b3912b0c8dfe.camel@intel.com> (raw)
In-Reply-To: <20230411171651.1067966-3-seanjc@google.com>
On Tue, 2023-04-11 at 10:16 -0700, Sean Christopherson wrote:
> +Timeline
> +~~~~~~~~
> +Submissions are typically reviewed and applied in FIFO order, with some wiggle
> +room for the size of a series, patches that are "cache hot", etc. Fixes,
> +especially for the current release and or stable trees, get to jump the queue.
> +Patches that will be taken through a non-KVM tree (most often through the tip
> +tree) and/or have other acks/reviews also jump the queue to some extent.
> +
> +Note, the vast majority of review is done between rc1 and rc6, give or take.
> +The period between rc6 and the next rc1 is used to catch up on other tasks,
> +i.e. radio silence during this period isn't unusual.
> +
> +Pings to get a status update are welcome, but keep in mind the timing of the
> +current release cycle and have realistic expectations. If you are pinging for
> +acceptance, i.e. not just for feedback or an update, please do everything you
> +can, within reason, to ensure that your patches are ready to be merged! Pings
> +on series that break the build or fail tests lead to unhappy maintainers!
> +
It seems you don't like resending patch as a ping:
https://lore.kernel.org/lkml/20230410031021.4145297-1-alexjlzheng@tencent.com/t/#md30aa77e5c2592b5b1fb0401d14e6fdbf52c2e06
Do you want to include this to the documentation too?
next prev parent reply other threads:[~2023-04-12 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 17:16 [PATCH v3 0/2] Documentation/process: Add a maintainer handbook for KVM x86 Sean Christopherson
2023-04-11 17:16 ` [PATCH v3 1/2] Documentation/process: Add a label for the tip tree handbook's coding style Sean Christopherson
2023-04-11 17:16 ` [PATCH v3 2/2] Documentation/process: Add a maintainer handbook for KVM x86 Sean Christopherson
2023-04-12 10:04 ` Huang, Kai [this message]
2023-04-12 15:47 ` Sean Christopherson
2023-04-19 7:37 ` Like Xu
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=4e3706bd9dccc6cd00eab9c59e06b3912b0c8dfe.camel@intel.com \
--to=kai.huang@intel.com \
--cc=aaronlewis@google.com \
--cc=aghulati@google.com \
--cc=amoorthy@google.com \
--cc=ashish.kalra@amd.com \
--cc=axelrasmussen@google.com \
--cc=babu.moger@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bgardon@google.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenyi.qiang@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dmatlack@google.com \
--cc=dwmw@amazon.co.uk \
--cc=eesposit@redhat.com \
--cc=erdemaktas@google.com \
--cc=flyingpenghao@gmail.com \
--cc=gshan@redhat.com \
--cc=guang.zeng@intel.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=jiaxi.chen@linux.intel.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=jthoughton@google.com \
--cc=junaids@google.com \
--cc=kvm@vger.kernel.org \
--cc=leobras@redhat.com \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=maciej.szmigiero@oracle.com \
--cc=mhal@rbox.co \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=mizhang@google.com \
--cc=mlevitsk@redhat.com \
--cc=nikunj@amd.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=pdurrant@amazon.com \
--cc=peterx@redhat.com \
--cc=pgonda@google.com \
--cc=pshier@google.com \
--cc=ricarkol@google.com \
--cc=robert.hu@linux.intel.com \
--cc=sagis@google.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vipinsh@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.w.wang@intel.com \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhenzhong.duan@intel.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