From: Link Mauve <linkmauve@linkmauve.fr>
To: Link Mauve <linkmauve@linkmauve.fr>
Cc: "Srinivas Kandagatla" <srini@kernel.org>,
"Sasha Finkelstein" <k@chaosmail.tech>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Sven Peter" <sven@kernel.org>, "Janne Grunau" <j@jannau.net>,
"Neal Gompa" <neal@gompa.dev>, "Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Vladimir Zapolskiy" <vz@mleia.com>,
"André Draszik" <andre.draszik@linaro.org>,
"Orson Zhai" <orsonzhai@gmail.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Chunyan Zhang" <zhang.lyra@gmail.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Kalyani Akula" <kalyani.akula@amd.com>,
"Michal Simek" <michal.simek@amd.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Johan Hovold" <johan@kernel.org>,
"Ronald Claveau" <linux-kernel-dev@aliel.fr>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, imx@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v6 0/4] nvmem: migrate to const void * in reg_write
Date: Sun, 20 Sep 2026 13:18:45 +0200 [thread overview]
Message-ID: <aq_BFQ4wgnJqGngQ@desktop> (raw)
In-Reply-To: <20260920111000.2404131-1-linkmauve@linkmauve.fr>
Oops, I forgot to carry the tag I got in v5…
Here it is:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
On Sun, Sep 20, 2026 at 01:09:53PM +0200, Link Mauve wrote:
> This callback used to take a mutable void * for no reason, which causes
> the compiler to be unaware that the val buffer should never be modified
> by the callback.
>
> This was found while drafting the nvmem-provider Rust abstraction.
>
> Thanks to the guidance of Andy Shevchenko, this now introduces a new
> callback and deprecates the existing one, with the goal of renaming the
> new one into the old one once no user remains in the kernel.
>
> Changes since v5:
> - Link to v5:
> https://lore.kernel.org/rust-for-linux/20260804135940.2378737-1-linkmauve@linkmauve.fr/T/
> - Add a dev_warn() when registering a nvmem driver with a deprecated
> reg_write callback.
> - Add a fourth patch enabling COMPILE_TEST on three more nvmem drivers,
> which forgot to depend on that config.
> - Remove a few unneeded (void *) and (const void *) casts in core.c.
>
> Changes since v4:
> - Link to v4:
> https://lore.kernel.org/rust-for-linux/20260726131724.15299-1-linkmauve@linkmauve.fr/T/
> - Rebase on top of linux-next 20260803, the previous series didn’t apply
> any more due to changes in core.c.
> - Also convert the at24, at25, eeprom_93xx46 and m24lr drivers to the
> new reg_write_const callback, these were missed because they got moved
> to the nvmem directory in linux-next between v3 and v4.
>
> Changes since v3:
> - Link to v3:
> https://lore.kernel.org/rust-for-linux/20260716142415.28718-1-linkmauve@linkmauve.fr/T/
> - Drop Apple SPMI patch, which had already been independently included
> in linux-next as 7089170e1df160f5f8fb395bc5aa2e2697b4e896.
> - Reword the cover letter’s subject.
> - Reorder the meson firmware patch before the other ones, so that every
> commit is always working correctly.
>
> Changes since v2:
> - Link to v2:
> https://lore.kernel.org/rust-for-linux/aljAqBNVXV1aVJqx@luna/T/
> - Rebase on top of linux-next/master.
> - Fix logic error which made all devices read-only.
> - Remove a blanket cast of function pointers to void * in
> apple-spmi-nvmem (patch 3).
> - Also fix constness of write buffer in firmware: meson, which is used
> exclusively by meson-efuse (patch 4).
> - Re-review all changes to make sure the passed types are more correct
> than they were before.
> - Actually test with COMPILE_TEST, which I forgot to enable before…
>
> Changes since v1:
> - Link to v1:
> https://lore.kernel.org/rust-for-linux/20260715175229.24672-1-linkmauve@linkmauve.fr/
> - Removed all changes to other subsystems than nvmem.
> - Added a new reg_write_const callback instead of changing the exisitng
> reg_write.
> - Deprecated the existing reg_write callback, it will get removed once
> all users in the kernel will be done migrating to the new one.
>
> Link Mauve (4):
> firmware: meson: pass a const buffer to meson_sm_call_write()
> nvmem: core: deprecate reg_write callback with reg_write_const
> nvmem: make all reg_write callbacks take const void *
> nvmem: enable COMPILE_TEST for more drivers
>
> drivers/firmware/meson/meson_sm.c | 2 +-
> drivers/nvmem/Kconfig | 6 +++---
> drivers/nvmem/apple-spmi-nvmem.c | 4 ++--
> drivers/nvmem/at24.c | 6 +++---
> drivers/nvmem/at25.c | 4 ++--
> drivers/nvmem/bcm-ocotp.c | 8 ++++----
> drivers/nvmem/core.c | 26 ++++++++++++++++---------
> drivers/nvmem/eeprom_93xx46.c | 6 +++---
> drivers/nvmem/imx-ocotp-scu.c | 6 +++---
> drivers/nvmem/imx-ocotp.c | 6 +++---
> drivers/nvmem/internals.h | 1 +
> drivers/nvmem/lan9662-otpc.c | 6 +++---
> drivers/nvmem/lpc18xx_eeprom.c | 6 +++---
> drivers/nvmem/m24lr.c | 4 ++--
> drivers/nvmem/max77759-nvmem.c | 4 ++--
> drivers/nvmem/meson-efuse.c | 8 ++++----
> drivers/nvmem/qcom-spmi-sdam.c | 6 +++---
> drivers/nvmem/qfprom.c | 6 +++---
> drivers/nvmem/rave-sp-eeprom.c | 6 +++---
> drivers/nvmem/snvs_lpgpr.c | 4 ++--
> drivers/nvmem/sprd-efuse.c | 6 +++---
> drivers/nvmem/stm32-bsec-optee-ta.c | 2 +-
> drivers/nvmem/stm32-bsec-optee-ta.h | 4 ++--
> drivers/nvmem/stm32-romem.c | 10 +++++-----
> drivers/nvmem/zynqmp_nvmem.c | 6 +++---
> include/linux/firmware/meson/meson_sm.h | 2 +-
> include/linux/nvmem-provider.h | 6 +++++-
> 27 files changed, 87 insertions(+), 74 deletions(-)
>
>
> base-commit: 3f2425f5b5bbbdd991ca9cdfd5502e68d8895998
> --
> 2.55.0
>
--
Link Mauve
prev parent reply other threads:[~2026-09-20 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 11:09 Link Mauve
2026-09-20 11:09 ` [PATCH v6 1/4] firmware: meson: pass a const buffer to meson_sm_call_write() Link Mauve
2026-09-20 11:09 ` [PATCH v6 2/4] nvmem: core: deprecate reg_write callback with reg_write_const Link Mauve
2026-09-20 11:09 ` [PATCH v6 3/4] nvmem: make all reg_write callbacks take const void * Link Mauve
2026-09-20 11:09 ` [PATCH v6 4/4] nvmem: enable COMPILE_TEST for more drivers Link Mauve
2026-09-20 11:18 ` Link Mauve [this message]
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=aq_BFQ4wgnJqGngQ@desktop \
--to=linkmauve@linkmauve.fr \
--cc=Frank.Li@nxp.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alexandre.torgue@foss.st.com \
--cc=aliceryhl@google.com \
--cc=andre.draszik@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=asahi@lists.linux.dev \
--cc=baolin.wang@linux.alibaba.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=daniel.lezcano@kernel.org \
--cc=festevam@gmail.com \
--cc=gary@garyguo.net \
--cc=imx@lists.linux.dev \
--cc=j@jannau.net \
--cc=jbrunet@baylibre.com \
--cc=johan@kernel.org \
--cc=k@chaosmail.tech \
--cc=kalyani.akula@amd.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel-dev@aliel.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lossin@kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michal.simek@amd.com \
--cc=neal@gompa.dev \
--cc=neil.armstrong@linaro.org \
--cc=ojeda@kernel.org \
--cc=orsonzhai@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=srini@kernel.org \
--cc=sven@kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=vz@mleia.com \
--cc=work@onurozkan.dev \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®