From: Lee Jones <lee@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Pavel Machek <pavel@ucw.cz>, Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
linux-leds@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: cros_ec: Implement review comments from Lee
Date: Thu, 20 Jun 2024 13:27:41 +0100 [thread overview]
Message-ID: <20240620122741.GL3029315@google.com> (raw)
In-Reply-To: <5708f5c6-65fe-4bf9-8d08-6dbb77e21a9d@t-8ch.de>
On Thu, 20 Jun 2024, Thomas Weißschuh wrote:
> Hi Lee,
>
> On 2024-06-20 10:31:14+0000, Lee Jones wrote:
> > Definitely not seen a commit message like that before
>
> I assumed that this patch would be squashed into the original commit.
>
> My question in which form you wanted the changes should have included
> "incremental series".
Incremental means on top.
A lot of maintainers don't support history re-writes, but I've reserved
that right since forever, so I can squash it if you like.
> > > Implement review comments from Lee as requested in [0] for
> > > "leds: Add ChromeOS EC driver".
> > >
> > > Changes:
> > > * Inline DRV_NAME string constant.
> > > * Use dev_err() instead of dev_warn() to report errors.
> > > * Rename cros_ec_led_probe_led() to cros_ec_led_probe_one().
> > > * Make loop variable "int" where they belong.
> > > * Move "Unknown LED" comment to where it belongs.
> > > * Register trigger during _probe().
> > > * Use module_platform_driver() and drop all the custom boilerplate.
> >
> > If you're fixing many things, then I would expect to receive many
> > patches. One patch for functional change please. If you can reasonably
> > group fixes of similar elk, then please do. However one patch that does
> > a bunch of different things is a no-go from me, sorry.
>
> Absolutely, if these changes are to end up as actual commits then they
> need to look different.
> I'll resend them as proper series.
>
> > > [0] https://lore.kernel.org/lkml/20240614093445.GF3029315@google.com/T/#m8750abdef6a968ace765645189170814196c9ce9
> > >
> > > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > > ---
> > > drivers/leds/leds-cros_ec.c | 50 +++++++++++++--------------------------------
> > > 1 file changed, 14 insertions(+), 36 deletions(-)
>
> <snip>
>
> Sorry for the confusion,
> Thomas
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-06-20 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 10:04 [PATCH] leds: cros_ec: Implement review comments from Lee Thomas Weißschuh
2024-06-20 9:31 ` Lee Jones
2024-06-20 10:12 ` Thomas Weißschuh
2024-06-20 12:27 ` Lee Jones [this message]
2024-06-20 14:38 ` Thomas Weißschuh
2024-06-20 17:15 ` Lee Jones
2024-06-20 19:02 ` Thomas Weißschuh
2024-06-21 10:40 ` Lee Jones
2024-06-21 10:44 ` Thomas Weißschuh
2024-06-20 17:13 ` (subset) " 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=20240620122741.GL3029315@google.com \
--to=lee@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=pavel@ucw.cz \
/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.