Date:   Thu, 9 Mar 2023 09:37:45 +0700
From:   Bagas Sanjaya <bagasdotme@gmail.com>
To:     Sean Christopherson <seanjc@google.com>,
        Paolo Bonzini <pbonzini@redhat.com>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        Sagi Shahar <sagis@google.com>,
        Erdem Aktas <erdemaktas@google.com>,
        Peter Shier <pshier@google.com>,
        Anish Ghulati <aghulati@google.com>,
        Oliver Upton <oliver.upton@linux.dev>,
        James Houghton <jthoughton@google.com>,
        Anish Moorthy <amoorthy@google.com>,
        Ben Gardon <bgardon@google.com>,
        David Matlack <dmatlack@google.com>,
        Ricardo Koller <ricarkol@google.com>,
        Axel Rasmussen <axelrasmussen@google.com>,
        Aaron Lewis <aaronlewis@google.com>,
        Ashish Kalra <ashish.kalra@amd.com>,
        Babu Moger <babu.moger@amd.com>, Chao Gao <chao.gao@intel.com>,
        Chao Peng <chao.p.peng@linux.intel.com>,
        Chenyi Qiang <chenyi.qiang@intel.com>,
        David Woodhouse <dwmw@amazon.co.uk>,
        Emanuele Giuseppe Esposito <eesposit@redhat.com>,
        Gavin Shan <gshan@redhat.com>,
        Guang Zeng <guang.zeng@intel.com>,
        Hou Wenlong <houwenlong.hwl@antgroup.com>,
        Jiaxi Chen <jiaxi.chen@linux.intel.com>,
        Jim Mattson <jmattson@google.com>,
        Jing Liu <jing2.liu@intel.com>,
        Junaid Shahid <junaids@google.com>,
        Kai Huang <kai.huang@intel.com>,
        Leonardo Bras <leobras@redhat.com>,
        Like Xu <like.xu.linux@gmail.com>,
        Li RongQing <lirongqing@baidu.com>,
        "Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
        Maxim Levitsky <mlevitsk@redhat.com>,
        Michael Roth <michael.roth@amd.com>,
        Michal Luczaj <mhal@rbox.co>,
        Mingwei Zhang <mizhang@google.com>,
        Nikunj A Dadhania <nikunj@amd.com>,
        Paul Durrant <pdurrant@amazon.com>,
        Peng Hao <flyingpenghao@gmail.com>,
        Peter Gonda <pgonda@google.com>, Peter Xu <peterx@redhat.com>,
        Robert Hoo <robert.hu@linux.intel.com>,
        Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
        Tom Lendacky <thomas.lendacky@amd.com>,
        Vipin Sharma <vipinsh@google.com>,
        Vitaly Kuznetsov <vkuznets@redhat.com>,
        Wanpeng Li <wanpengli@tencent.com>,
        Wei Wang <wei.w.wang@intel.com>,
        Xiaoyao Li <xiaoyao.li@intel.com>,
        Yu Zhang <yu.c.zhang@linux.intel.com>,
        Zhenzhong Duan <zhenzhong.duan@intel.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Documentation/process: Add a maintainer handbook
 for KVM x86
Message-ID: <ZAlGeYAmvhPmVmGe@debian.me>
References: <20230309010336.519123-1-seanjc@google.com>
 <20230309010336.519123-3-seanjc@google.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="NDWV0Qdh3JqbrY46"
Content-Disposition: inline
In-Reply-To: <20230309010336.519123-3-seanjc@google.com>
Precedence: bulk


--NDWV0Qdh3JqbrY46
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 08, 2023 at 05:03:36PM -0800, Sean Christopherson wrote:
> +As a general guideline, use ``kvm-x86/next`` even if a patch/series touc=
hes
> +multiple architectures, i.e. isn't strictly scoped to x86.  Using any of=
 the
> +branches from the main KVM tree is usually a less good option as they li=
kely
> +won't have many, if any, changes for the next release, i.e. using the ma=
in KVM
> +tree as a base is more likely to yield conflicts.  And if there are non-=
trivial
> +conflicts with multiple architectures, coordination between maintainers =
will be
> +required no matter what base is used.  Note, this is far from a hard rul=
e, i.e.
> +use a different base for multi-arch series if that makes the most sense.

That means patches that primarily kvm ARM changes should be based on
kvm-x86/next, right?

> +If a patch touches multiple topics, traverse up the conceptual tree to f=
ind the
> +first common parent (which is often simply ``x86``).  When in doubt,
> +``git log path/to/file`` should provide a reasonable hint.

What do you mean by conceptual tree? Is it Patch subject prefix?

> +KVM selftests that are associated with KVM changes, e.g. regression test=
s for
> +bug fixes, should be posted along with the KVM changes as a single serie=
s.  The
> +standard kernel rules for bisection apply, i.e. KVM changes that result =
in test
> +failures should be ordered after the selftests updates, and vice versa, =
new
> +tests that fail due to KVM bugs should be ordered after the KVM fixes.

Did you mean that in a patch series, selftest patches are placed after
their corresponding KVM changes?

Thanks.

--=20
An old man doll... just what I always wanted! - Clara

--NDWV0Qdh3JqbrY46
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZAlGdAAKCRD2uYlJVVFO
o+TdAP9DJ67tjIQE98q87j5y5QSunga8EATx+tybmWc+J/G3VQD/S5M66oNorefy
PI6e/pSeetKmqTEqlxuLlylfAHb0Vgo=
=yhsP
-----END PGP SIGNATURE-----

--NDWV0Qdh3JqbrY46--