From: Marc Zyngier <maz@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: 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>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: name the kvmarm/kvmarm next branch
Date: Thu, 24 Sep 2026 07:59:21 +0100 [thread overview]
Message-ID: <877bkb3zjq.wl-maz@kernel.org> (raw)
In-Reply-To: <20260924033536.3624334-1-matthias.goergens@gmail.com>
On Thu, 24 Sep 2026 04:35:36 +0100,
Matthias Goergens <matthias.goergens@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.
next prev parent reply other threads:[~2026-09-24 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 3:35 [PATCH] MAINTAINERS: name the kvmarm/kvmarm next branch Matthias Goergens
2026-09-24 6:59 ` Marc Zyngier [this message]
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-25 8:58 ` sashiko-bot
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=877bkb3zjq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=matthias.goergens@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.