[PATCH v2] Documentation/process: Add a maintainer entry profile for KVM/arm64

Marc Zyngier maz at kernel.org
Mon Nov 2 00:05:25 PST 2026


On Mon, 02 Nov 2026 07:16:47 +0000,
Krzysztof Kozlowski <krzk at kernel.org> wrote:
> 
> 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.

No. People use whatever they want to use, and we don't have to be
prescriptive.

>
> ...
> 
> > +
> > +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.

I'm perfectly happy to have this here. Most people will only read the
one document they need to (if any). And I really doubt that the
mention of a nested guest escape is that common (as a basic grep would
have shown you).

	M.

-- 
Without deviation from the norm, progress is not possible.



More information about the linux-arm-kernel mailing list