linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"Uwe Kleine-König" <uwe@kleine-koenig.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Minghao Chi" <chi.minghao@zte.com.cn>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Angel Iglesias" <ang.iglesiasg@gmail.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Lee Jones" <lee.jones@linaro.org>
Subject: Re: [PATCH 289/606] macintosh: ams/ams-i2c: Convert to i2c's .probe_new()
Date: Sat, 19 Nov 2022 11:16:02 +0100	[thread overview]
Message-ID: <20221119101602.kfreiw4mdbjf7prj@pengutronix.de> (raw)
In-Reply-To: <1d2ae1bb-d4ba-35cf-63b6-f23a0187a223@csgroup.eu>

[-- Attachment #1: Type: text/plain, Size: 2768 bytes --]

Hello Christophe,

On Sat, Nov 19, 2022 at 07:38:58AM +0000, Christophe Leroy wrote:
> Le 18/11/2022 à 23:40, Uwe Kleine-König a écrit :
> > From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > 
> > The probe function doesn't make use of the i2c_device_id * parameter so it
> > can be trivially converted.
> > 
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> The patch itself and the others seems ok. But can you group all 
> macintosh changes into a single patch instead of the 9 patches you sent ?
> 
> See the process about submitting patches, 
> https://docs.kernel.org/process/submitting-patches.html and especially 
> the "NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org 
> people!" and the associated reference 
> https://lore.kernel.org/all/20050711.125305.08322243.davem@davemloft.net/ :
> 
> 	If you feel the need to send, say, more than 15 patches at once, 
> reconsider.

Thanks for your feedback.

Let me point out in response to the request to squash patches together
that this wish doesn't seem to be the universal right thing to do.

Last time I did a conversion grouped by subsystem, one of the replies
was:

	Reviewed-by: ...
	if you split on per driver basis.

(https://lore.kernel.org/linux-iio/20220808085526.280066-1-u.kleine-koenig@pengutronix.de)

The obvious upside of a split per driver is that the individual bits are
easier to review, an Ack can be limited to a certain set of drivers, and
(probably most important): If a driver later gets a commit that needs
backporting, a patch that only touches this single driver can more
easily be backported as a dependency.

Also the request to not send everything at once but keep back some
patches has an obvious downside. I.e. I have to restart yet more often
to rebase + test to get all patches applied in the end. And you could
argue that the sum of the work load on the mail servers doesn't get
smaller in sum if the 600 patches are sent over (say) 2 months.
(To prevent a flame war here: Yeah, I agree there are downsides of a
single big series, too.)

All in all my personal opinion is that the advantages of a split per
driver slightly outweight the disadvantages. But obviously that's
subjective.

I will wait a while before sending updates to this series, so don't
expect a new patch very soon. (This has the nice effect that it gives
you some time to reconsider your argument and maybe apply the patches as
they are now, preventing another mail to the lists with the cumulated
macintosh changes ;-)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

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

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

Thread overview: 39+ 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:40 ` [PATCH 289/606] macintosh: ams/ams-i2c: Convert to i2c's .probe_new() Uwe Kleine-König
2022-11-19  7:38   ` Christophe Leroy
2022-11-19 10:16     ` Uwe Kleine-König [this message]
2022-11-18 22:40 ` [PATCH 290/606] macintosh: therm_adt746x: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 291/606] macintosh: therm_windtunnel: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 292/606] macintosh: windfarm_ad7417_sensor: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 293/606] macintosh: windfarm_fcu_controls: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 294/606] macintosh: windfarm_lm75_sensor: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 295/606] macintosh: windfarm_lm87_sensor: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 296/606] macintosh: windfarm_max6690_sensor: " Uwe Kleine-König
2022-11-18 22:40 ` [PATCH 297/606] macintosh: windfarm_smu_sat: " Uwe Kleine-König
2022-11-18 22:45 ` [PATCH 597/606] ALSA: aoa: onyx: " Uwe Kleine-König
2022-11-19  8:44   ` Takashi Iwai
2022-11-18 22:45 ` [PATCH 598/606] ALSA: aoa: tas: " Uwe Kleine-König
2022-11-19  8:45   ` Takashi Iwai
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
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-11-30  9:23 ` Michael Ellerman
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=20221119101602.kfreiw4mdbjf7prj@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ang.iglesiasg@gmail.com \
    --cc=chi.minghao@zte.com.cn \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).