public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Eddie James" <eajames@linux.ibm.com>,
	"Jeremy Kerr" <jk@ozlabs.org>,
	"Alistar Popple" <alistair@popple.id.au>,
	linux-fsi@lists.ozlabs.org, kernel@pengutronix.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsi: i2cr: Switch to use struct i2c_driver's .probe()
Date: Mon, 21 Aug 2023 07:48:28 +0200	[thread overview]
Message-ID: <2023082119-volatile-vacation-ec45@gregkh> (raw)
In-Reply-To: <CACPK8XdP=t4fLioXE=hnxN_oA1Qyo9VZxjqoUSnNCBErWKRXEQ@mail.gmail.com>

On Mon, Aug 21, 2023 at 04:57:52AM +0000, Joel Stanley wrote:
> On Wed, 16 Aug 2023 at 17:20, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
> >
> > struct i2c_driver::probe_new is about to go away. Switch the driver to
> > use the probe callback with the same prototype.
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > Hello,
> >
> > this driver appeared in next just today. I intend to drop .probe_new
> > from struct i2c_driver after v6.6-rc1, so it would be great if this
> > patch would go in together with the commit adding this driver.
> 
> Reviewed-by: Joel Stanley <joel@jms.id.au>
> 
> Greg, can you please take this for 6.6?

Yes, will do, thanks.

greg k-h

      reply	other threads:[~2023-08-21  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 17:19 [PATCH] fsi: i2cr: Switch to use struct i2c_driver's .probe() Uwe Kleine-König
2023-08-16 18:33 ` Eddie James
2023-08-21  4:57 ` Joel Stanley
2023-08-21  5:48   ` Greg Kroah-Hartman [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=2023082119-volatile-vacation-ec45@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alistair@popple.id.au \
    --cc=eajames@linux.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=kernel@pengutronix.de \
    --cc=linux-fsi@lists.ozlabs.org \
    --cc=linux-kernel@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