Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.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 2/2] iio: light: veml3328: remove extra blank line
Date: Sun, 26 Jul 2026 20:16:28 +0100	[thread overview]
Message-ID: <20260726201628.11fb4375@jic23-huawei> (raw)
In-Reply-To: <20260724-veml3328-cleanup-v1-2-240ecf3e5097@gmail.com>

On Fri, 24 Jul 2026 00:07:09 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:

> Remove an extra blank line in the iio_chan_spec[] assignment.
> 
> No functional change.

I don't mind this at one end of a series doing something more substantial
but patch 1 is going away anyway and this on it's own is too much
churn / noise.

Jonathan

> 
> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
> ---
>  drivers/iio/light/veml3328.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/iio/light/veml3328.c b/drivers/iio/light/veml3328.c
> index a65748466116..7884c8250590 100644
> --- a/drivers/iio/light/veml3328.c
> +++ b/drivers/iio/light/veml3328.c
> @@ -70,7 +70,6 @@ static const struct regmap_config veml3328_regmap_config = {
>  static const struct iio_chan_spec veml3328_channels[] = {
>  	{
>  		.type = IIO_LIGHT,
> -
>  		.info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
>  		.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE),
>  		.info_mask_shared_by_type_available = BIT(IIO_CHAN_INFO_SCALE),
> 


      reply	other threads:[~2026-07-26 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 22:07 [PATCH 0/2] iio: light: veml3328: minor cleanup fixes Joshua Crofts
2026-07-23 22:07 ` [PATCH 1/2] iio: light: veml3328: remove unused i2c_set_clientdata() Joshua Crofts
2026-07-26 19:15   ` Jonathan Cameron
2026-07-23 22:07 ` [PATCH 2/2] iio: light: veml3328: remove extra blank line Joshua Crofts
2026-07-26 19:16   ` 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=20260726201628.11fb4375@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=joshua.crofts1@gmail.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