From: Jianhua Lu <lujianhua000@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>, Lee Jones <lee@kernel.org>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
kernel@pengutronix.de
Subject: Re: [PATCH] backlight: ktz8866: Convert to i2c's .probe_new()
Date: Sun, 29 Jan 2023 01:35:07 +0800 [thread overview]
Message-ID: <Y9Vcy/U1jbGtDQ7p@Gentoo> (raw)
In-Reply-To: <20230128170708.om77umvc43bmskgv@pengutronix.de>
On Sat, Jan 28, 2023 at 06:07:08PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Sun, Jan 29, 2023 at 12:44:30AM +0800, Jianhua Lu wrote:
> > On Sat, Jan 28, 2023 at 05:16:13PM +0100, Uwe Kleine-König wrote:
> > > I don't want to squash the changes to the ktz8866 driver into the patch
> > > that modifies struct i2c_driver, as this needlessly clutters the commit,
> > > if it's that what you wanted. (There are more than 1000 i2c drivers and
> > > the others are not converted in a single lockstep, too.)
> >
> > Do't squash this patch, I'd like you send a series patch instead of
> > a single patch.
>
> This series was already sent before. However that happend based on a
> tree that didn't contain the ktz8866 backlight driver, so this patch
> came later (and I didn't resend the whole series for the two drivers
> that were added since then :-). See
> https://lore.kernel.org/lkml/20221118224540.619276-1-uwe@kleine-koenig.org.
> for the original post.
Thanks for explanation.
>
> Letting this patch go in via the i2c tree together with the commit
> changing i2c_driver is fine for me, it won't be the only one.
I think so too.
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | https://www.pengutronix.de/ |
next prev parent reply other threads:[~2023-01-28 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:26 [PATCH] backlight: ktz8866: Convert to i2c's .probe_new() Uwe Kleine-König
2023-01-27 15:26 ` Uwe Kleine-König
2023-01-28 0:36 ` Jianhua Lu
2023-01-28 0:36 ` Jianhua Lu
2023-01-28 13:32 ` Uwe Kleine-König
2023-01-28 14:14 ` Jianhua Lu
2023-01-28 16:16 ` Uwe Kleine-König
2023-01-28 16:44 ` Jianhua Lu
2023-01-28 17:07 ` Uwe Kleine-König
2023-01-28 17:35 ` Jianhua Lu [this message]
2023-01-30 9:42 ` Lee Jones
2023-01-30 9:42 ` Lee Jones
2023-02-11 23:05 ` Uwe Kleine-König
2023-02-22 15:23 ` Lee Jones
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=Y9Vcy/U1jbGtDQ7p@Gentoo \
--to=lujianhua000@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lee@kernel.org \
--cc=linux-fbdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.