From: Marc Zyngier <maz@kernel.org>
To: Luo Jie <quic_luoj@quicinc.com>
Cc: Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Julia Lawall <Julia.Lawall@inria.fr>,
"Nicolas\ Palix" <nicolas.palix@imag.fr>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>, <linux-kernel@vger.kernel.org>,
<cocci@inria.fr>, <linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.linux.dev>, <andrew@lunn.ch>,
<quic_kkumarcs@quicinc.com>, <quic_linchen@quicinc.com>,
<quic_leiwei@quicinc.com>, <quic_suruchia@quicinc.com>,
<quic_pavir@quicinc.com>
Subject: Re: [PATCH v4 0/5] Add FIELD_MODIFY() helper
Date: Thu, 12 Jun 2025 15:11:33 +0100 [thread overview]
Message-ID: <86sek5cane.wl-maz@kernel.org> (raw)
In-Reply-To: <20250612-field_modify-v4-0-ae4f74da45a6@quicinc.com>
On Thu, 12 Jun 2025 14:46:07 +0100,
Luo Jie <quic_luoj@quicinc.com> wrote:
>
> Add the helper FIELD_MODIFY() to the FIELD_XXX family of bitfield
> macros. It is functionally similar as xxx_replace_bits(), but adds
> the compile time checking to catch incorrect parameter type errors.
>
> This series also converts the four instances of opencoded FIELD_MODIFY()
> that are found in the core kernel files, to instead use the new
> FIELD_MODIFY() macro. This is achieved with Coccinelle, by adding
> the script field_modify.cocci.
>
> The changes are validated on IPQ9574 SoC which uses ARM64 architecture.
>
> Signed-off-by: Luo Jie <quic_luoj@quicinc.com>
I already indicated that the *pre-existing* set of helpers are enough
for what we want to do, that we *already* use them for KVM/arm64, and
that I didn't need nor want two ways to do the same thing in the same
code base.
My opinion hasn't changed on that front, and I don't see a point in
these patches.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-06-12 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 13:46 [PATCH v4 0/5] Add FIELD_MODIFY() helper Luo Jie
2025-06-12 13:46 ` [PATCH v4 1/5] coccinelle: misc: Add field_modify script Luo Jie
2025-06-12 16:48 ` [cocci] " Markus Elfring
2025-06-16 10:28 ` Luo Jie
2025-06-12 13:46 ` [PATCH v4 2/5] arm64: tlb: Convert the opencoded field modify Luo Jie
2025-06-12 20:15 ` [cocci] " Markus Elfring
2025-06-16 10:37 ` Luo Jie
2025-06-16 10:41 ` Will Deacon
2025-06-16 16:19 ` Luo Jie
2025-06-16 13:52 ` [cocci] [v4 " Markus Elfring
2025-06-16 16:19 ` Luo Jie
2025-06-12 13:46 ` [PATCH v4 3/5] arm64: nvhe: " Luo Jie
2025-06-12 13:46 ` [PATCH v4 4/5] arm64: kvm: " Luo Jie
2025-06-12 13:46 ` [PATCH v4 5/5] arm64: mm: " Luo Jie
2025-06-12 14:11 ` Marc Zyngier [this message]
2025-06-16 10:06 ` [PATCH v4 0/5] Add FIELD_MODIFY() helper Luo Jie
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=86sek5cane.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=cocci@inria.fr \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=nicolas.palix@imag.fr \
--cc=oliver.upton@linux.dev \
--cc=quic_kkumarcs@quicinc.com \
--cc=quic_leiwei@quicinc.com \
--cc=quic_linchen@quicinc.com \
--cc=quic_luoj@quicinc.com \
--cc=quic_pavir@quicinc.com \
--cc=quic_suruchia@quicinc.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).