From: Hans de Goede <hdegoede@redhat.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: "Corey Minyard" <cminyard@mvista.com>,
"Peter Senna Tschudin" <peter.senna@gmail.com>,
"Haowen Bai" <baihaowen@meizu.com>,
linux-media@vger.kernel.org, "Tom Rix" <trix@redhat.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
linux-staging@lists.linux.dev,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
"Adrien Grassein" <adrien.grassein@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
kernel@pengutronix.de, "Jean Delvare" <jdelvare@suse.de>
Subject: Re: [PATCH v2 2/5] media: atomisp: Switch i2c drivers back to use .probe()
Date: Sun, 11 Jun 2023 21:16:41 +0200 [thread overview]
Message-ID: <d2d2bc9b-9d75-d96b-d6fe-8a4bfa532a27@redhat.com> (raw)
In-Reply-To: <20230611110749.jujuc2j6qx2nlihy@pengutronix.de>
Hi Uwe,
On 6/11/23 13:07, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, May 24, 2023 at 05:16:43PM +0200, Uwe Kleine-König 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>
>
> the four other patches from this series are already in next, this one
> wasn't picked up yet though. There is another change for staging: media:
> atomisp in next via Mauro's media-next (branch: fixes).
>
> Who wants/should pick up this change?
This patch is already in media-staging:
https://git.linuxtv.org/media_stage.git/log/?ofs=50
https://git.linuxtv.org/media_stage.git/commit/?id=625ac9af384481e8644e0653a4aa472aa95f0395
So this is on its way to -next already.
Regards,
Hans
next prev parent reply other threads:[~2023-06-11 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 15:16 [PATCH v2 0/5] staging: Switch i2c drivers back to use .probe() Uwe Kleine-König
2023-05-24 15:16 ` [PATCH v2 1/5] staging: iio: " Uwe Kleine-König
2023-05-28 16:41 ` Jonathan Cameron
2023-05-24 15:16 ` [PATCH v2 2/5] media: atomisp: " Uwe Kleine-König
2023-05-24 16:05 ` Hans de Goede
2023-06-11 11:07 ` Uwe Kleine-König
2023-06-11 19:16 ` Hans de Goede [this message]
2023-06-11 19:58 ` Uwe Kleine-König
2023-05-24 15:16 ` [PATCH v2 3/5] media: staging: max96712: Switch i2c driver " Uwe Kleine-König
2023-05-24 15:16 ` [PATCH v2 4/5] staging: olpc_dcon: " Uwe Kleine-König
2023-05-24 15:16 ` [PATCH v2 5/5] staging: most: " 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=d2d2bc9b-9d75-d96b-d6fe-8a4bfa532a27@redhat.com \
--to=hdegoede@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=adrien.grassein@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=baihaowen@meizu.com \
--cc=cminyard@mvista.com \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=jdelvare@suse.de \
--cc=kernel@pengutronix.de \
--cc=khalasa@piap.pl \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=peter.senna@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=trix@redhat.com \
--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