From: Lee Jones <lee@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Pavel Machek" <pavel@ucw.cz>, "Kate Hsuan" <hpa@redhat.com>,
"Sebastian Reichel" <sre@kernel.org>,
platform-driver-x86@vger.kernel.org,
"André Apitzsch" <git@apitzsch.eu>,
linux-leds@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [GIT PULL] Immutable branch between LEDs, Power and RGB due for the v6.11 merge window
Date: Fri, 31 May 2024 14:54:23 +0100 [thread overview]
Message-ID: <20240531135423.GM1005600@google.com> (raw)
In-Reply-To: <20240531114124.45346-1-hdegoede@redhat.com>
Enjoy!
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git ib-leds-platform-power-v6.11
for you to fetch changes up to 9af12f57f1f9785f231d31a7365ad244c656b7ff:
power: supply: power-supply-leds: Add charging_orange_full_green trigger for RGB LED (2024-05-31 12:57:43 +0100)
----------------------------------------------------------------
Immutable branch between LEDs, Power and RGB due for the v6.11 merge window
----------------------------------------------------------------
Hans de Goede (3):
leds: rgb: leds-ktd202x: Initialize mutex earlier
leds: core: Add led_mc_set_brightness() function
leds: trigger: Add led_mc_trigger_event() function
Kate Hsuan (3):
leds: rgb: leds-ktd202x: Get device properties through fwnode to support ACPI
leds: rgb: leds-ktd202x: I2C ID tables for KTD2026 and 2027
power: supply: power-supply-leds: Add charging_orange_full_green trigger for RGB LED
drivers/leds/led-class-multicolor.c | 1 +
drivers/leds/led-core.c | 31 +++++++++++++
drivers/leds/led-triggers.c | 20 ++++++++
drivers/leds/rgb/Kconfig | 1 -
drivers/leds/rgb/leds-ktd202x.c | 80 ++++++++++++++++++--------------
drivers/power/supply/power_supply_leds.c | 23 +++++++++
include/linux/leds.h | 26 +++++++++++
include/linux/power_supply.h | 2 +
8 files changed, 149 insertions(+), 35 deletions(-)
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-05-31 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 11:41 [PATCH v10 0/6] KTD2026 indicator LED for X86 Xiaomi Pad2 Hans de Goede
2024-05-31 11:41 ` [PATCH v10 1/6] leds: rgb: leds-ktd202x: Get device properties through fwnode to support ACPI Hans de Goede
2024-05-31 11:41 ` [PATCH v10 2/6] leds: rgb: leds-ktd202x: I2C ID tables for KTD2026 and 2027 Hans de Goede
2024-05-31 11:41 ` [PATCH v10 3/6] leds: rgb: leds-ktd202x: Initialize mutex earlier Hans de Goede
2024-05-31 11:41 ` [PATCH v10 4/6] leds: core: Add led_mc_set_brightness() function Hans de Goede
2024-05-31 11:41 ` [PATCH v10 5/6] leds: trigger: Add led_mc_trigger_event() function Hans de Goede
2024-05-31 11:41 ` [PATCH v10 6/6] power: supply: power-supply-leds: Add charging_orange_full_green trigger for RGB LED Hans de Goede
2024-05-31 12:01 ` [PATCH v10 0/6] KTD2026 indicator LED for X86 Xiaomi Pad2 Lee Jones
2024-05-31 12:02 ` Lee Jones
2024-05-31 13:54 ` Lee Jones [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=20240531135423.GM1005600@google.com \
--to=lee@kernel.org \
--cc=andy@kernel.org \
--cc=git@apitzsch.eu \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@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).