From: Mark Brown <broonie@kernel.org>
To: Angel Iglesias <ang.iglesiasg@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Wolfram Sang <wsa@kernel.org>,
Uwe Kleine-König <uwe@kleine-koenig.org>
Cc: linux-input@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-staging@lists.linux.dev, linux-spi@vger.kernel.org,
linux-iio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-crypto@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-leds@vger.kernel.org,
netdev@vger.kernel.org, linux-pm@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-fbdev@vger.kernel.org, linux-i2c@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
platform-driver-x86@vger.kernel.org,
linux-actions@lists.infradead.org, linux-mtd@lists.infradead.org,
linux-serial@vger.kernel.org, chrome-platform@lists.linux.dev,
openipmi-developer@lists.sourceforge.net,
alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-integrity@vger.kernel.org,
kernel@pengutronix.de, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, Purism Kernel Team <kernel@puri.sm>,
linux-usb@vger.kernel.org
Subject: Re: (subset) [PATCH 000/606] i2c: Complete conversion to i2c_probe_new
Date: Thu, 24 Nov 2022 13:26:51 +0000 [thread overview]
Message-ID: <166929641104.251383.2794823399583000124.b4-ty@kernel.org> (raw)
In-Reply-To: <20221118224540.619276-1-uwe@kleine-koenig.org>
On Fri, 18 Nov 2022 23:35:34 +0100, Uwe Kleine-König wrote:
> since commit b8a1a4cd5a98 ("i2c: Provide a temporary .probe_new()
> call-back type") from 2016 there is a "temporary" alternative probe
> callback for i2c drivers.
>
> This series completes all drivers to this new callback (unless I missed
> something). It's based on current next/master.
> A part of the patches depend on commit 662233731d66 ("i2c: core:
> Introduce i2c_client_get_device_id helper function"), there is a branch that
> you can pull into your tree to get it:
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[538/606] regulator: act8865-regulator: Convert to i2c's .probe_new()
(no commit info)
[539/606] regulator: ad5398: Convert to i2c's .probe_new()
commit: 7f69edba960bbdcbc829d8d0995b1117ce29e8b1
[540/606] regulator: da9121-regulator: Convert to i2c's .probe_new()
commit: 020cf73b47414a84b666d3e6736a6ae957e27840
[541/606] regulator: fan53555: Convert to i2c's .probe_new()
(no commit info)
[542/606] regulator: isl6271a-regulator: Convert to i2c's .probe_new()
(no commit info)
[543/606] regulator: lp3972: Convert to i2c's .probe_new()
commit: 2532d5f8d5c20d5a0a8a0d57a311bc5df00dea04
[544/606] regulator: lp872x: Convert to i2c's .probe_new()
commit: 87feccb347b25f5dc6ff451123b832c9ad5dddfe
[545/606] regulator: lp8755: Convert to i2c's .probe_new()
commit: cb28f74b4809a00b40fdf0c44ccf51ab950581d3
[546/606] regulator: ltc3589: Convert to i2c's .probe_new()
commit: 78c8f6cdb51d471928d481ed3b2c82dbc110a1ed
[547/606] regulator: max1586: Convert to i2c's .probe_new()
commit: 3d54f7ba248b0ad1791bc356e9ad3d9020a1c472
[548/606] regulator: max8649: Convert to i2c's .probe_new()
commit: 3cf4417385d0ac8f02f22888e12a6d21d97d89fc
[549/606] regulator: max8660: Convert to i2c's .probe_new()
commit: dbf31dac703009174226bb87b3914bd092040327
[550/606] regulator: max8952: Convert to i2c's .probe_new()
commit: c20c36735949b3b7984692fbab3d92b0e8a845ec
[551/606] regulator: max8973-regulator: Convert to i2c's .probe_new()
commit: 4e85e5d64f66ac5e4b0286ee4b6f8e8ce1044d42
[552/606] regulator: pca9450-regulator: Convert to i2c's .probe_new()
commit: ed56fa6e804cb13bbe29e9214792308817f6e553
[553/606] regulator: pfuze100-regulator: Convert to i2c's .probe_new()
(no commit info)
[554/606] regulator: pv88080-regulator: Convert to i2c's .probe_new()
(no commit info)
[555/606] regulator: rpi-panel-attiny-regulator: Convert to i2c's .probe_new()
commit: d85d02d17a608b558d44510e9824668c5d4fe5d8
[556/606] regulator: tps51632-regulator: Convert to i2c's .probe_new()
commit: d4885f306304ff29eec06b9ad5f526a1099e0418
[557/606] regulator: tps62360-regulator: Convert to i2c's .probe_new()
commit: 18804160277ec2ab992373385f86c6af2322b28b
[558/606] regulator: tps6286x-regulator: Convert to i2c's .probe_new()
commit: e34782316281c78c5911f86d4699d4f35a607c9d
[559/606] regulator: tps65023-regulator: Convert to i2c's .probe_new()
commit: 3b5b07dde998f6ade7433a8db019cf816c7e35af
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-11-24 13:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 22:35 [PATCH 000/606] i2c: Complete conversion to i2c_probe_new Uwe Kleine-König
2022-11-18 22:43 ` [PATCH 496/606] mtd: maps: pismo: Convert to i2c's .probe_new() Uwe Kleine-König
2023-02-01 12:13 ` Richard Weinberger
2022-11-19 6:50 ` [PATCH 000/606] i2c: Complete conversion to i2c_probe_new patchwork-bot+chrome-platform
2022-11-19 6:50 ` patchwork-bot+chrome-platform
2022-11-19 11:10 ` Wolfram Sang
2022-11-20 19:43 ` Sebastian Reichel
2022-11-21 9:53 ` Lee Jones
2022-11-22 18:58 ` Jonathan Cameron
2022-11-22 20:16 ` Uwe Kleine-König
2022-11-26 15:43 ` Andy Shevchenko
2022-11-23 12:11 ` (subset) " Mark Brown
2022-11-23 17:23 ` Mark Brown
2022-11-24 12:27 ` Mark Brown
2022-11-24 13:26 ` Mark Brown [this message]
2022-11-24 13:50 ` Mark Brown
2022-11-24 14:03 ` Mark Brown
2022-11-24 14:28 ` Mark Brown
2022-11-24 15:15 ` Mark Brown
2022-11-24 15:26 ` Mark Brown
2022-11-24 15:38 ` Mark Brown
2022-11-24 15:49 ` Mark Brown
2022-11-24 16:04 ` Mark Brown
2022-11-25 14:27 ` Mark Brown
2022-12-09 12:00 ` Robert Foss
2022-12-12 16:36 ` Robert Foss
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=166929641104.251383.2794823399583000124.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ang.iglesiasg@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=lee.jones@linaro.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=patches@opensource.cirrus.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=uwe@kleine-koenig.org \
--cc=wsa@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).