From: Matthias Goergens <matthias.goergens@gmail.com>
To: 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>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev
Subject: [PATCH] MAINTAINERS: name the kvmarm/kvmarm next branch
Date: Thu, 24 Sep 2026 11:35:36 +0800 [thread overview]
Message-ID: <20260924033536.3624334-1-matthias.goergens@gmail.com> (raw)
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.
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.
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index cc3cae2e378b..8394e0a1c149 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14301,7 +14301,7 @@ R: Zenghui Yu <yuzenghui@huawei.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
L: kvmarm@lists.linux.dev
S: Maintained
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next
F: Documentation/virt/kvm/arm/
F: Documentation/virt/kvm/devices/arm*
F: arch/arm64/include/asm/kvm*
base-commit: 40288c9206c17eb66a603262e06a58d300d0f279
--
2.55.0
next reply other threads:[~2026-09-24 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 3:35 Matthias Goergens [this message]
2026-09-24 6:59 ` [PATCH] MAINTAINERS: name the kvmarm/kvmarm next branch Marc Zyngier
2026-09-24 8:30 ` Matthias Goergens
2026-09-24 13:33 ` Marc Zyngier
2026-09-25 8:56 ` [RFC PATCH] Documentation/process: Add a maintainer entry profile for KVM/arm64 Matthias Goergens
2026-09-27 10:22 ` Marc Zyngier
2026-10-05 12:10 ` Oliver Upton
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=20260924033536.3624334-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--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