From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: Fix set_id_regs selftest for ASIDBITS becoming unwritable
Date: Tue, 17 Dec 2024 13:54:39 +0000 [thread overview]
Message-ID: <86v7viqusg.wl-maz@kernel.org> (raw)
In-Reply-To: <53b40aa8-f51c-4c4e-a4ad-e6a9512e5197@sirena.org.uk>
On Tue, 17 Dec 2024 13:12:12 +0000,
Mark Brown <broonie@kernel.org> wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> On Tue, Dec 17, 2024 at 08:30:37AM +0000, Marc Zyngier wrote:
> > Mark Brown <broonie@kernel.org> wrote:
>
> > > Fixes: 03c7527e97f7 ("KVM: arm64: Do not allow ID_AA64MMFR0_EL1.ASIDbits to be overridden")
>
> > A patch for a test doesn't fix anything in the kernel.
>
> The selftests are shipped as part of the kernel source and frequently
> used for testing the kernel, it's all one source base and we want to
> ensure that for example the test fix gets backported if the relevant
> kernel patch does.
That's not what Fixes: describes. If you want to invent a new tag that
expresses a dependency, do that. Don't use these tags to misrepresent
what the patches does.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-12-17 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 19:28 [PATCH] KVM: arm64: Fix set_id_regs selftest for ASIDBITS becoming unwritable Mark Brown
2024-12-17 8:30 ` Marc Zyngier
2024-12-17 13:12 ` Mark Brown
2024-12-17 13:54 ` Marc Zyngier [this message]
2024-12-17 15:10 ` Mark Brown
2024-12-17 15:55 ` Marc Zyngier
2024-12-17 18:00 ` Oliver Upton
2024-12-17 19:22 ` Mark Brown
2024-12-17 9:19 ` 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=86v7viqusg.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--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.