From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Kevin Tsai" <ktsai@capellamicro.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: light: cm3232: make struct cm3232_als_info const
Date: Sun, 6 Jul 2025 10:51:34 +0100 [thread overview]
Message-ID: <20250706105134.0f327b3a@jic23-huawei> (raw)
In-Reply-To: <20250628-iio-const-data-20-v1-0-2bf90b03f9f1@baylibre.com>
On Sat, 28 Jun 2025 12:52:29 -0500
David Lechner <dlechner@baylibre.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,
prev parent reply other threads:[~2025-07-06 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 17:52 [PATCH 0/2] iio: light: cm3232: make struct cm3232_als_info const David Lechner
2025-06-28 17:52 ` [PATCH 1/2] iio: light: cm3232: move calibscale to struct cm3232_chip David Lechner
2025-06-28 17:52 ` [PATCH 2/2] iio: light: cm3232: make struct cm3232_als_info const David Lechner
2025-07-06 9:51 ` Jonathan Cameron [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=20250706105134.0f327b3a@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=ktsai@capellamicro.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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