public inbox for chrome-platform@lists.linux.dev
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Benson Leung <bleung@chromium.org>, Lee Jones <lee@kernel.org>,
	Guenter Roeck <groeck@chromium.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] platform/chrome: cros_kbd_led_backlight: Some cleanups
Date: Tue, 7 Apr 2026 06:19:25 +0000	[thread overview]
Message-ID: <adSh7Uh3lJusWOKT@google.com> (raw)
In-Reply-To: <20260404-cros_kbd_led-cleanup-v1-0-0dc1100d54e3@weissschuh.net>

On Sat, Apr 04, 2026 at 09:55:25AM +0200, Thomas Weißschuh wrote:
> Some cleanups for the cros_kbd_led_backlight driver.
> 
> Patches 1-3 should go through platform-chrome.
> Patch 4 and 5 should go either through platform-chrome or MFD.

The series looks good to me.  I plan to apply at least patches 1-3 after
v7.1-rc1.

      parent reply	other threads:[~2026-04-07  6:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  7:55 [PATCH 0/5] platform/chrome: cros_kbd_led_backlight: Some cleanups Thomas Weißschuh
2026-04-04  7:55 ` [PATCH 1/5] platform/chrome: cros_kbd_led_backlight: Drop max_brightness from driver data Thomas Weißschuh
2026-04-04  7:55 ` [PATCH 2/5] platform/chrome: cros_kbd_led_backlight: Pass keyboard_led as parameter Thomas Weißschuh
2026-04-04  7:55 ` [PATCH 3/5] platform/chrome: cros_kbd_led_backlight: Drop CONFIG_MFD_CROS_EC_DEV ifdeffery Thomas Weißschuh
2026-04-04  7:55 ` [PATCH 4/5] mfd: cros_ec: Add a helper to retrieve the EC device from the MFD parent Thomas Weißschuh
2026-04-04  7:55 ` [PATCH 5/5] platform/chrome: cros_kbd_led_backlight: Use cros_ec_mfd_get_ec_dev() Thomas Weißschuh
2026-04-07  6:19 ` Tzung-Bi Shih [this message]

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=adSh7Uh3lJusWOKT@google.com \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    /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