linux-kernel - Re: [PATCH 0/2] iio: light: cm3232: make struct cm3232_als

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250706105134.0f327b3a@jic23-huawei>
Date: Sun, 6 Jul 2025 10:51:34 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Kevin Tsai <ktsai@...ellamicro.com>, Nuno Sá
 <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
 linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] iio: light: cm3232: make struct cm3232_als_info
 const

On Sat, 28 Jun 2025 12:52:29 -0500
David Lechner <dlechner@...libre.com> wrote:

> Typically, chip info structs are const. Before we can make that change,
> we need to move the calibscale field to the driver data struct. This
> also allows individual instances of the driver to have different
> calibscale values.
> 
> ---
> David Lechner (2):
>       iio: light: cm3232: move calibscale to struct cm3232_chip
>       iio: light: cm3232: make struct cm3232_als_info const
Applied.

> 
>  drivers/iio/light/cm3232.c | 18 ++++++++----------
>  1 file changed, 8 insertions(+), 10 deletions(-)
> ---
> base-commit: 14071b9cf2d751ff9bc8b5e43fa94fbf08aceea1
> change-id: 20250628-iio-const-data-20-1f1a05001890
> 
> Best regards,