Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "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: proximity: vcnl3020: make vcnl3020_property const
Date: Sun, 29 Jun 2025 18:22:04 +0100	[thread overview]
Message-ID: <20250629182204.68dfa4ec@jic23-huawei> (raw)
In-Reply-To: <20250628-iio-const-data-25-v1-0-5d99cf17790e@baylibre.com>

On Sat, 28 Jun 2025 13:23:47 -0500
David Lechner <dlechner@baylibre.com> wrote:

> We can make const struct vcnl3020_property vcnl3020_led_current_property
> const since it is read-only data. For this to really be useful, we also
> have another change to pass this struct by pointer instead of by value.
> 
Applied to the testing branch of iio.git.

Thanks,

Jonathan

> ---
> David Lechner (2):
>       iio: proximity: vcnl3020: pass struct vcnl3020_property by pointer
>       iio: proximity: vcnl3020: make vcnl3020_property const
> 
>  drivers/iio/proximity/vcnl3020.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> ---
> base-commit: 14071b9cf2d751ff9bc8b5e43fa94fbf08aceea1
> change-id: 20250628-iio-const-data-25-452e9458133b
> 
> Best regards,


      parent reply	other threads:[~2025-06-29 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 18:23 [PATCH 0/2] iio: proximity: vcnl3020: make vcnl3020_property const David Lechner
2025-06-28 18:23 ` [PATCH 1/2] iio: proximity: vcnl3020: pass struct vcnl3020_property by pointer David Lechner
2025-06-28 18:23 ` [PATCH 2/2] iio: proximity: vcnl3020: make vcnl3020_property const David Lechner
2025-06-29 17:22 ` 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=20250629182204.68dfa4ec@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.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