All of lore.kernel.org
 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, kernel@pengutronix.de
Subject: Re: [PATCH] iio: Switch i2c drivers back to use .probe()
Date: Sat, 20 May 2023 17:54:11 +0100	[thread overview]
Message-ID: <20230520175411.790a4dd2@jic23-huawei> (raw)
In-Reply-To: <20230520164340.25360292@jic23-huawei>

On Sat, 20 May 2023 16:43:40 +0100
Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 15 May 2023 22:50:48 +0200
> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> 
> > After commit b8a1a4cd5a98 ("i2c: Provide a temporary .probe_new()
> > call-back type"), all drivers being converted to .probe_new() and then
> > 03c835f498b5 ("i2c: Switch .probe() to not take an id parameter") convert
> > back to (the new) .probe() to be able to eventually drop .probe_new() from
> > struct i2c_driver.
> > 
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>  
> Some fuzz due to other patches being queued up already, but otherwise
> LGTM and applied to the togreg branch of iio.git which is initially pushed
> out as testing for 0-day to give it a whirl.
> 
> Thanks,
> 
> Jonathan

I'm seeing some bounces due to size of email. 

It's in the testing branch of iio.git if anyone wants to see what was in this patch!

https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=testing&id=be8e2ed93211e39a2b70e8a3f268beefd517d222

  parent reply	other threads:[~2023-05-20 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 20:50 [PATCH] iio: Switch i2c drivers back to use .probe() Uwe Kleine-König
     [not found] ` <20230520164340.25360292@jic23-huawei>
2023-05-20 16:54   ` Jonathan Cameron [this message]
2023-05-20 17:13   ` Uwe Kleine-König
2023-05-21 17:56     ` Jonathan Cameron
2023-05-26 15:51       ` Uwe Kleine-König

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=20230520175411.790a4dd2@jic23-huawei \
    --to=jic23@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.