From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>
Cc: 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>,
Zenghui Yu <yuzenghui@huawei.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: Mon, 2 Nov 2026 08:16:47 +0100 [thread overview]
Message-ID: <8ffc41d7-b032-481c-9643-a87847b8452b@kernel.org> (raw)
In-Reply-To: <20261030083351.3040604-1-matthias.goergens@gmail.com>
On 30/10/2026 09:33, Matthias Goergens wrote:
> +
> +If your series depends on something else that is not yet in mainline, such as
> +another series under review, say so in the cover letter and name exactly what
> +it applies on top of.
> +
> +Use ``git format-patch --base`` so that the base commit is recorded in the
> +patches.
You should rather encourage usage of b4, which does above for you.
...
> +
> +Security issues
> +---------------
> +
> +Bugs that let a guest attack its host, or a nested guest attack its guest
> +hypervisor, should be reported as described in
> +Documentation/process/security-bugs.rst.
Do we need to repeat standard stuff in every maintainer profile? Above
is quite obvious, so maybe skip it which would make the document shorter
increasing the chances anyone will read it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-02 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 8:33 [PATCH v2] Documentation/process: Add a maintainer entry profile for KVM/arm64 Matthias Goergens
2026-10-30 9:51 ` Zenghui Yu
2026-10-31 21:03 ` Wei-Lin Chang
2026-11-02 8:37 ` Matthias Goergens
2026-11-02 18:59 ` Marc Zyngier
2026-11-02 7:16 ` Krzysztof Kozlowski [this message]
2026-11-02 8:05 ` Marc Zyngier
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=8ffc41d7-b032-481c-9643-a87847b8452b@kernel.org \
--to=krzk@kernel.org \
--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 \
--cc=yuzenghui@huawei.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