From: Zenghui Yu <yuzenghui@huawei.com>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>, <kvmarm@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>, Randy Dunlap <rdunlap@infradead.org>,
<linux-kernel@vger.kernel.org>, <workflows@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation/process: Add a maintainer entry profile for KVM/arm64
Date: Fri, 30 Oct 2026 17:51:17 +0800 [thread overview]
Message-ID: <cc52465a-54b8-12ca-ec5f-fa1aa1c0c55d@huawei.com> (raw)
In-Reply-To: <20261030083351.3040604-1-matthias.goergens@gmail.com>
Hi Matthias,
On 2026/10/30 16:33, Matthias Goergens wrote:
> KVM/arm64 has no P: entry in MAINTAINERS, so nothing tells a contributor
> that the kvmarm tree is used for integration only, or what the
> maintainers expect patches to be based on. Marc Zyngier said a profile
> would help.
>
> Add one covering the trees, the base for patches, the submit checklist,
> key cycle dates and review cadence, and point the KVM/arm64 entry at it.
>
> Link: https://lore.kernel.org/all/875wzu4vuv.wl-maz@kernel.org/
> Link: https://lore.kernel.org/all/87tsnb2dtq.wl-maz@kernel.org/
> Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
> ---
> Changes since the RFC
> (https://lore.kernel.org/all/20260925085621.562448-1-matthias.goergens@gmail.com/):
>
> - Point at the MAINTAINERS entry instead of naming maintainers and lists.
> - Describe master, topic branches and shared branches; drop the open
> questions, which the RFC's Sashiko review had also flagged.
> - Base: prefer -rc1 to -rc3, not kvmarm/next; leave conflicts visible.
> - Subject lines: capital letter after the prefixes.
> - Architecture references: prefer rule identifiers; drop the comparison
> with KVM x86.
> - Testing: selftests usually at the end of the series, reproducible
> performance measurements, tests encouraged rather than required for NV.
> - Key cycle dates: no new features after -rc6; how fixes are sent.
> - Review cadence: stability of commit IDs; answering bot reviews.
> - Posted as a new thread, with the documentation maintainers and lists
> on Cc.
>
> Steffen, Marc asked you for a short addition on KVM/arm64 on s390 for
> the Trees section. I've left it out and can add it as a follow-up.
>
> Oliver, thanks for inviting an updated patch. Corrections are welcome.
>
> .../process/maintainer-kvm-arm64.rst | 181 ++++++++++++++++++
> MAINTAINERS | 2 +
> 2 files changed, 183 insertions(+)
> create mode 100644 Documentation/process/maintainer-kvm-arm64.rst
This looks pretty good. Thanks a lot for your efforts!
Acked-by: Zenghui Yu <yuzenghui@huawei.com>
prev parent reply other threads:[~2026-10-30 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:33 Matthias Goergens
2026-10-30 9:51 ` Zenghui Yu [this message]
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=cc52465a-54b8-12ca-ec5f-fa1aa1c0c55d@huawei.com \
--to=yuzenghui@huawei.com \
--cc=corbet@lwn.net \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.goergens@gmail.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=rdunlap@infradead.org \
--cc=seiden@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=workflows@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
all inboxes | Powered by JetHome®