public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Angel Iglesias <ang.iglesiasg@gmail.com>,
	Lee Jones <lee.jones@linaro.org>,
	Grant Likely <grant.likely@linaro.org>,
	linux-i2c@vger.kernel.org, kernel@pengutronix.de,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-crypto@vger.kernel.org, linux-gpio@vger.kernel.org,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	linux-rpi-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
	linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-leds@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-media@vger.kernel.org, patches@opensource.cirrus.com,
	linux-actions@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	linux-amlogic@lists.infradead.org, alsa-devel@alsa-project.org,
	linux-omap@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-mtd@lists.infradead.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
	linux-pm@vger.kernel.org, Purism Kernel Team <kernel@puri.sm>,
	linux-pwm@vger.kernel.org, linux-rtc@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-serial@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-fbdev@vger.kernel.org, linux-watchdog@vger.kernel.org,
	openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH 000/606] i2c: Complete conversion to i2c_probe_new
Date: Sat, 19 Nov 2022 12:10:11 +0100	[thread overview]
Message-ID: <Y3i5kz6IL7tFbVwX@shikoro> (raw)
In-Reply-To: <20221118224540.619276-1-uwe@kleine-koenig.org>


[-- Attachment #1.1: Type: text/plain, Size: 647 bytes --]

Hi Uwe,

> This series completes all drivers to this new callback (unless I missed
> something). It's based on current next/master.

Thanks for this work, really, but oh my poor inbox...

> I don't think it's feasable to apply this series in one go, so I ask the
> maintainers of the changed files to apply via their tree.

This seems reasonable. It would have made sense to send "patch series
per subsystem" then. So people only see the subset they are interested
in. I know filename-to-subsys mapping is hardly ever perfect. But in my
experience, even imperfect, it is more convenient than such a huge patch
series.

Happy hacking,

   Wolfram


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-11-19 11:11 UTC|newest]

Thread overview: 40+ 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:35 ` [PATCH 002/606] tpm: tpm_i2c_atmel: Convert to i2c's .probe_new() Uwe Kleine-König
2022-11-28  1:15   ` Jarkko Sakkinen
2022-11-18 22:35 ` [PATCH 006/606] crypto: atmel-ecc - " Uwe Kleine-König
2022-11-25  9:46   ` Herbert Xu
2022-11-18 22:35 ` [PATCH 007/606] crypto: atmel-sha204a " Uwe Kleine-König
2022-11-25  9:46   ` Herbert Xu
2022-11-18 22:36 ` [PATCH 043/606] drm/panel: raspberrypi-touchscreen: " Uwe Kleine-König
2022-12-22 22:59   ` Javier Martinez Canillas
2023-01-10 10:12   ` Javier Martinez Canillas
2022-11-18 22:39 ` [PATCH 209/606] Input: atmel_captouch - " Uwe Kleine-König
2022-12-06 10:49   ` Jean Delvare
2022-11-18 22:39 ` [PATCH 260/606] Input: stmfts " Uwe Kleine-König
2022-11-18 22:43 ` [PATCH 460/606] mfd: stmfx: " Uwe Kleine-König
2022-11-18 22:43 ` [PATCH 461/606] mfd: stmpe-i2c: " Uwe Kleine-König
2022-11-18 22:45 ` [PATCH 584/606] usb: typec: ucsi: stm32g0: " Uwe Kleine-König
2022-11-21  9:09   ` Heikki Krogerus
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 [this message]
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
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=Y3i5kz6IL7tFbVwX@shikoro \
    --to=wsa@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 \
    /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