Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org,
	Robert Eshleman <bobbyeshleman@gmail.com>,
	kernel@pengutronix.de
Subject: Re: [PATCH] iio: light: max44009: Convert to i2c's .probe_new()
Date: Fri, 23 Dec 2022 14:04:15 +0000	[thread overview]
Message-ID: <20221223140415.36064aed@jic23-huawei> (raw)
In-Reply-To: <20221222145429.614781-1-u.kleine-koenig@pengutronix.de>

On Thu, 22 Dec 2022 15:54:29 +0100
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:

> The probe function doesn't make use of the i2c_device_id * parameter so
> it can be trivially converted.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> since the series that mass converted drivers to probe_new this driver
> was added with the old probe prototype. Fix is accordingly.

Nope, this driver has been there since 2019.  It's the one that I failed
to pick up your patch for originally.  I have it queued up for the coming
cycle, but not pushed out for next yet because I want to rebase my tree
on rc1 first.

Jonathan

> 
> Best regards
> Uwe
> 
>  drivers/iio/light/max44009.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/iio/light/max44009.c b/drivers/iio/light/max44009.c
> index 801e5a0ad496..3dadace09fe2 100644
> --- a/drivers/iio/light/max44009.c
> +++ b/drivers/iio/light/max44009.c
> @@ -487,8 +487,7 @@ static irqreturn_t max44009_threaded_irq_handler(int irq, void *p)
>  	return IRQ_NONE;
>  }
>  
> -static int max44009_probe(struct i2c_client *client,
> -			  const struct i2c_device_id *id)
> +static int max44009_probe(struct i2c_client *client)
>  {
>  	struct max44009_data *data;
>  	struct iio_dev *indio_dev;
> @@ -538,7 +537,7 @@ static struct i2c_driver max44009_driver = {
>  	.driver = {
>  		.name = MAX44009_DRV_NAME,
>  	},
> -	.probe = max44009_probe,
> +	.probe_new = max44009_probe,
>  	.id_table = max44009_id,
>  };
>  module_i2c_driver(max44009_driver);
> 
> base-commit: 9d2f6060fe4c3b49d0cdc1dce1c99296f33379c8


  reply	other threads:[~2022-12-23 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 14:54 [PATCH] iio: light: max44009: Convert to i2c's .probe_new() Uwe Kleine-König
2022-12-23 14:04 ` Jonathan Cameron [this message]
2022-12-23 17:32   ` Uwe Kleine-König
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10 16:18 [PATCH] iio: light : max44009 : " Anup Sharma
2023-01-10 17:07 ` Jonathan Cameron

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=20221223140415.36064aed@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=bobbyeshleman@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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