From: Marc Zyngier <maz@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Wei-Lin Chang <weilin.chang@arm.com>,
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>,
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, 02 Nov 2026 18:59:08 +0000 [thread overview]
Message-ID: <868q3b2h6r.wl-maz@kernel.org> (raw)
In-Reply-To: <20261102083759.1561867-1-matthias.goergens@gmail.com>
On Mon, 02 Nov 2026 08:37:59 +0000,
Matthias Goergens <matthias.goergens@gmail.com> wrote:
>
> On Sat, 31 Oct 2026 21:03:17 +0000, Wei-Lin Chang wrote:
> >> +Minor problems are often fixed up by the maintainers when applying; if they
> >> +say "no need to resend", don't.
> >
> > The second half of this is a little silly :P
> > What about just:
> >
> > Minor problems are often fixed up by the maintainers when applying; ask
> > if you are unsure whether to resend.
>
> Agreed, that reads better. I'll use your wording in v3.
If that's the only change, I'll fix it when applying.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-11-02 18:59 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 [this message]
2026-11-02 7:16 ` Krzysztof Kozlowski
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=868q3b2h6r.wl-maz@kernel.org \
--to=maz@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=oupton@kernel.org \
--cc=rdunlap@infradead.org \
--cc=seiden@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@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 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.