public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Erikas Bitovtas <xerikasxx@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Peter Meerwald" <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 6/6] iio: light: vcnl4000: use variables for I2C client and device instances
Date: Mon, 16 Mar 2026 12:39:34 +0200	[thread overview]
Message-ID: <abfd5pLsCuPK4lV3@ashevche-desk.local> (raw)
In-Reply-To: <20260314-vcnl4000-regulators-v3-6-3c4a48d30676@gmail.com>

On Sat, Mar 14, 2026 at 06:06:35PM +0200, Erikas Bitovtas wrote:
> After moving data->client and client->dev into variables of their own,
> replace all instances of data->client and client->dev being used in
> vcnl4200_init and vcnl4000_probe by the said variables to reduce
> clutter.

...

> -	ret = i2c_smbus_write_word_data(data->client, VCNL4200_PS_CONF1,
> +	ret = i2c_smbus_write_word_data(client, VCNL4200_PS_CONF1,
>  					regval);

Now it's perfectly a single line.

	ret = i2c_smbus_write_word_data(client, VCNL4200_PS_CONF1, regval);

>  	if (ret < 0)
>  		return ret;

...

>  	regval = ret | VCNL4040_CONF3_PS_SAMPLE_16BITS;
> -	ret = i2c_smbus_write_word_data(data->client, VCNL4200_PS_CONF3,
> +	ret = i2c_smbus_write_word_data(client, VCNL4200_PS_CONF3,
>  					regval);

Ditto.

>  	if (ret < 0)
>  		return ret;

> -	if (device_property_read_u32(&client->dev, "proximity-near-level",
> +	if (device_property_read_u32(dev, "proximity-near-level",
>  				     &data->near_level))
>  		data->near_level = 0;

The 'if' is redundant, I think you can drop it at some point, probably to avoid
churn in the follow up

 -	if (device_property_read_u32(&client->dev, "proximity-near-level",
 -		data->near_level = 0;
 +	device_property_read_u32(dev, "proximity-near-level", &data->near_level);

Assuming data is allocated with kzalloc() or equivalent.

...

> -		ret = devm_iio_triggered_buffer_setup(&client->dev, indio_dev,
> +		ret = devm_iio_triggered_buffer_setup(dev, indio_dev,
>  						      NULL,

Now NULL can be moved to upper line.

>  						      data->chip_spec->trig_buffer_func,
>  						      data->chip_spec->buffer_setup_ops);

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-16 10:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14 16:06 [PATCH v3 0/6] iio: light: vcnl4000: add regulator support Erikas Bitovtas
2026-03-14 16:06 ` [PATCH v3 1/6] dt-bindings: iio: light: vcnl4000: add regulators Erikas Bitovtas
2026-03-15  8:49   ` Krzysztof Kozlowski
2026-03-15 17:07     ` Erikas Bitovtas
2026-03-14 16:06 ` [PATCH v3 2/6] iio: light: vcnl4000: sort includes by their name Erikas Bitovtas
2026-03-14 16:06 ` [PATCH v3 3/6] iio: light: vcnl4000: replace mutex_init with devm_mutex_init Erikas Bitovtas
2026-03-14 19:51   ` David Lechner
2026-03-15 18:26   ` Jonathan Cameron
2026-03-16 10:24   ` Andy Shevchenko
2026-03-14 16:06 ` [PATCH v3 4/6] iio: light: vcnl4000: add support for regulators Erikas Bitovtas
2026-03-15 18:27   ` Jonathan Cameron
2026-03-16 10:27   ` Andy Shevchenko
2026-03-14 16:06 ` [PATCH v3 5/6] iio: light: vcnl4000: remove error messages for trigger and irq Erikas Bitovtas
2026-03-15 18:31   ` Jonathan Cameron
2026-03-15 19:15     ` Erikas Bitovtas
2026-03-15 21:24       ` Jonathan Cameron
2026-03-14 16:06 ` [PATCH v3 6/6] iio: light: vcnl4000: use variables for I2C client and device instances Erikas Bitovtas
2026-03-16 10:39   ` Andy Shevchenko [this message]
2026-03-16 10:50     ` Erikas Bitovtas
2026-03-16 11:10       ` Andy Shevchenko
2026-03-14 19:53 ` [PATCH v3 0/6] iio: light: vcnl4000: add regulator support David Lechner

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=abfd5pLsCuPK4lV3@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh@kernel.org \
    --cc=xerikasxx@gmail.com \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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