[PATCH] MAINTAINERS: name the kvmarm/kvmarm next branch

[Marc Zyngier]

On Thu, 24 Sep 2026 04:35:36 +0100,
Matthias Goergens <matthias.goergens at gmail.com> wrote:
> 
> The T: entry for KERNEL VIRTUAL MACHINE FOR ARM64 (KVM/arm64) names
> kvmarm/kvmarm without a branch.  The repository's HEAD (master,
> 0225fd5e0a6a) is a commit from 2020-05-01 that mainline already
> contains.  linux-next pulls next from this repository (Next/Trees,
> next-20260923), and on 2026-09-24 that branch carried work not yet in
> mainline.  Name the branch so the entry identifies where development
> happens.

But that's not reflecting the way we deal with this tree. No actual
development happens on that branch, as it is solely for integration.

Actually, no development happens in the kvmarm tree at all.

> 
> Documentation/process/submitting-patches.rst sends contributors to the
> T: entry to find the tree to prepare patches against, so a branch-less
> entry whose HEAD is already in mainline points them at the wrong tree.

Again, this is not how we work. We explicitly discourage patches
against -next. The only sane reference to base kvmarm patches on is a
published upstream tag from Linus' tree.

	M.

-- 
Jazz isn't dead. It just smells funny.