linux-kernel - Re: [PATCH v3 2/2] Documentation/process: Add a maintainer handbook for KVM x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4e3706bd9dccc6cd00eab9c59e06b3912b0c8dfe.camel@intel.com>
Date:   Wed, 12 Apr 2023 10:04:33 +0000
From:   "Huang, Kai" <kai.huang@...el.com>
To:     "pbonzini@...hat.com" <pbonzini@...hat.com>,
        "Christopherson,, Sean" <seanjc@...gle.com>
CC:     "Li, Xiaoyao" <xiaoyao.li@...el.com>,
        "eesposit@...hat.com" <eesposit@...hat.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "pshier@...gle.com" <pshier@...gle.com>,
        "bagasdotme@...il.com" <bagasdotme@...il.com>,
        "jthoughton@...gle.com" <jthoughton@...gle.com>,
        "Zeng, Guang" <guang.zeng@...el.com>,
        "jmattson@...gle.com" <jmattson@...gle.com>,
        "leobras@...hat.com" <leobras@...hat.com>,
        "bgardon@...gle.com" <bgardon@...gle.com>,
        "pgonda@...gle.com" <pgonda@...gle.com>,
        "Liu, Jing2" <jing2.liu@...el.com>,
        "amoorthy@...gle.com" <amoorthy@...gle.com>,
        "nikunj@....com" <nikunj@....com>,
        "chao.p.peng@...ux.intel.com" <chao.p.peng@...ux.intel.com>,
        "Woodhouse, David" <dwmw@...zon.co.uk>,
        "mhal@...x.co" <mhal@...x.co>,
        "oliver.upton@...ux.dev" <oliver.upton@...ux.dev>,
        "mizhang@...gle.com" <mizhang@...gle.com>,
        "Shahar, Sagi" <sagis@...gle.com>,
        "michael.roth@....com" <michael.roth@....com>,
        "thomas.lendacky@....com" <thomas.lendacky@....com>,
        "aghulati@...gle.com" <aghulati@...gle.com>,
        "ricarkol@...gle.com" <ricarkol@...gle.com>,
        "bp@...en8.de" <bp@...en8.de>,
        "flyingpenghao@...il.com" <flyingpenghao@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "axelrasmussen@...gle.com" <axelrasmussen@...gle.com>,
        "robert.hu@...ux.intel.com" <robert.hu@...ux.intel.com>,
        "vkuznets@...hat.com" <vkuznets@...hat.com>,
        "vipinsh@...gle.com" <vipinsh@...gle.com>,
        "ashish.kalra@....com" <ashish.kalra@....com>,
        "Qiang, Chenyi" <chenyi.qiang@...el.com>,
        "suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
        "dmatlack@...gle.com" <dmatlack@...gle.com>,
        "aaronlewis@...gle.com" <aaronlewis@...gle.com>,
        "Szmigiero, Maciej" <maciej.szmigiero@...cle.com>,
        "peterx@...hat.com" <peterx@...hat.com>,
        "pdurrant@...zon.com" <pdurrant@...zon.com>,
        "wanpengli@...cent.com" <wanpengli@...cent.com>,
        "yu.c.zhang@...ux.intel.com" <yu.c.zhang@...ux.intel.com>,
        "junaids@...gle.com" <junaids@...gle.com>,
        "Aktas, Erdem" <erdemaktas@...gle.com>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "Duan, Zhenzhong" <zhenzhong.duan@...el.com>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "jiaxi.chen@...ux.intel.com" <jiaxi.chen@...ux.intel.com>,
        "Li, Rongqing" <lirongqing@...du.com>,
        "gshan@...hat.com" <gshan@...hat.com>,
        "like.xu.linux@...il.com" <like.xu.linux@...il.com>,
        "babu.moger@....com" <babu.moger@....com>,
        "Wang, Wei W" <wei.w.wang@...el.com>,
        "mlevitsk@...hat.com" <mlevitsk@...hat.com>,
        "houwenlong.hwl@...group.com" <houwenlong.hwl@...group.com>,
        "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
        "Gao, Chao" <chao.gao@...el.com>
Subject: Re: [PATCH v3 2/2] Documentation/process: Add a maintainer handbook
 for KVM x86

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?