Linux IIO development
 help / color / mirror / Atom feed
From: Stefan Windfeldt-Prytz <stefan.windfeldt-prytz@axis.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-iio@vger.kernel.org,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] iio: light: opt4001: Use i2c_get_match_data()
Date: Wed, 30 Aug 2023 10:17:44 +0200	[thread overview]
Message-ID: <ab94e388-2de2-f3ba-12ae-aad0e3a04eac@axis.com> (raw)
In-Reply-To: <20230812151908.188696-1-biju.das.jz@bp.renesas.com>

On 8/12/23 17:19, Biju Das wrote:
> Replace device_get_match_data()->i2c_get_match_data() to extend matching
> support for ID table.
> 
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
>   drivers/iio/light/opt4001.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/light/opt4001.c b/drivers/iio/light/opt4001.c
> index 502946bf9f94..6cf60151b3d8 100644
> --- a/drivers/iio/light/opt4001.c
> +++ b/drivers/iio/light/opt4001.c
> @@ -412,7 +412,7 @@ static int opt4001_probe(struct i2c_client *client)
>   	if (dev_id != OPT4001_DEVICE_ID_VAL)
>   		dev_warn(&client->dev, "Device ID: %#04x unknown\n", dev_id);
>   
> -	chip->chip_info = device_get_match_data(&client->dev);
> +	chip->chip_info = i2c_get_match_data(client);
>   
>   	indio_dev->channels = opt4001_channels;
>   	indio_dev->num_channels = ARRAY_SIZE(opt4001_channels);

Reviewed-by: Stefan Windfeldt-Prytz <stefan.windfeldt-prytz@axis.com>
Tested-by: Stefan Windfeldt-Prytz <stefan.windfeldt-prytz@axis.com>

      parent reply	other threads:[~2023-08-30 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 15:19 [PATCH] iio: light: opt4001: Use i2c_get_match_data() Biju Das
2023-08-28 16:23 ` Jonathan Cameron
2023-08-30  8:17 ` Stefan Windfeldt-Prytz [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=ab94e388-2de2-f3ba-12ae-aad0e3a04eac@axis.com \
    --to=stefan.windfeldt-prytz@axis.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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