From: Marc Zyngier <maz@kernel.org>
To: Ben Horgan <ben.horgan@arm.com>
Cc: catalin.marinas@arm.com, will@kernel.org, oliver.upton@linux.dev,
joey.gouly@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
shuah@kernel.org
Subject: Re: [PATCH v2 0/2] set_id_regs cleanup
Date: Tue, 25 Nov 2025 15:27:48 +0000 [thread overview]
Message-ID: <86cy56qgi3.wl-maz@kernel.org> (raw)
In-Reply-To: <20251125101207.1492580-1-ben.horgan@arm.com>
On Tue, 25 Nov 2025 10:12:05 +0000,
Ben Horgan <ben.horgan@arm.com> wrote:
>
> For this v2 I've dropped the ksft_test accounting fix. Mark Brown has
> more extensive changes [1] and looks to be a user of the set_id_regs
> test rather than someone just doing some cleanup. The other change in
> this series is to remove ARM64_FEATURE_FIELD_BITS from the tools
> sysreg.h header rather than the kernel version. I'll send a separate
> patch to remove the kernel version.
>
> Tidies up a few small things in set_id_regs. The removal of
> ARM64_FEATURE_FIELD_BITS touches other code only so much as it removes
> the define but set_id_regs.c is the only place its used.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-11-25 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:12 [PATCH v2 0/2] set_id_regs cleanup Ben Horgan
2025-11-25 10:12 ` [PATCH v2 1/2] KVM: arm64: selftests: Remove ARM64_FEATURE_FIELD_BITS and its last user Ben Horgan
2025-11-25 10:12 ` [PATCH v2 2/2] KVM: arm64: selftests: Consider all 7 possible levels of cache Ben Horgan
2025-11-25 15:27 ` Marc Zyngier [this message]
2025-11-25 18:31 ` [PATCH v2 0/2] set_id_regs cleanup Catalin Marinas
2025-11-25 19:45 ` Marc Zyngier
2025-11-25 21:28 ` Oliver Upton
2025-11-27 19:16 ` Catalin Marinas
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=86cy56qgi3.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@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.