[PATCH v5 0/3] nvmem: migrate to const void * in reg_write
Link Mauve
linkmauve at linkmauve.fr
Mon Sep 14 07:13:17 PDT 2026
Hi,
On Mon, Aug 17, 2026 at 09:54:43PM +0300, Andy Shevchenko wrote:
> On Tue, Aug 04, 2026 at 03:59:34PM +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.
>
> FWIW, if the approach taken is okay by maintainers,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko at intel.com>
Thanks for the review!
>
> I think this is right direction to go. We should use all possible ways to
> protect the data from corruption.
Sorry for not pinging again before the end of the 7.3 merge window, I
was on vacations, but this only delayed that work by one cycle.
Is there anything I could do to make it happen for 7.4, or should I just
wait until a maintainer picks up that series? I just tested and
everything still builds file on top of linux-next as of next-20260911.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
--
Link Mauve
More information about the linux-amlogic
mailing list