From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org, sfr@canb.auug.org.au
Cc: chrome-platform@lists.linux.dev, linux-next@vger.kernel.org,
srosek@chromium.org, rdunlap@infradead.org
Subject: Re: [PATCH 0/2] platform/chrome: cros_kbd_led_backlight: Fix dependencies
Date: Tue, 15 Apr 2025 02:45:45 +0000 [thread overview]
Message-ID: <Z_3IWd1fng3IV9bZ@google.com> (raw)
In-Reply-To: <20250414132427.204078-1-tzungbi@kernel.org>
On Mon, Apr 14, 2025 at 09:24:25PM +0800, Tzung-Bi Shih wrote:
> The first patch removes a redundant dependency.
>
> The second patch fixes the build errors discovered in [1].
>
> [1]: https://lore.kernel.org/chrome-platform/ed8adc69-c505-4108-bf63-92911b0395c7@infradead.org/T/#u
>
> Tzung-Bi Shih (2):
> platform/chrome: cros_kbd_led_backlight: Remove CROS_EC dependency
> platform/chrome: cros_kbd_led_backlight: Fix build dependencies
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/2] platform/chrome: cros_kbd_led_backlight: Remove CROS_EC dependency
commit: 9aea0edcc3e92f5c40184b96d004b4af5a8d264f
[2/2] platform/chrome: cros_kbd_led_backlight: Fix build dependencies
commit: 31d3bd592df5bf2912b8d97b0652ac3f0cd335cf
Thanks!
prev parent reply other threads:[~2025-04-15 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 13:24 [PATCH 0/2] platform/chrome: cros_kbd_led_backlight: Fix dependencies Tzung-Bi Shih
2025-04-14 13:24 ` [PATCH 1/2] platform/chrome: cros_kbd_led_backlight: Remove CROS_EC dependency Tzung-Bi Shih
2025-04-14 22:10 ` Randy Dunlap
2025-04-14 13:24 ` [PATCH 2/2] platform/chrome: cros_kbd_led_backlight: Fix build dependencies Tzung-Bi Shih
2025-04-14 22:11 ` Randy Dunlap
2025-04-15 2:35 ` Tzung-Bi Shih
2025-04-15 2:45 ` 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=Z_3IWd1fng3IV9bZ@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=srosek@chromium.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 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.