From: Lee Jones <lee@kernel.org>
To: Armin Wolf <W_Armin@gmx.de>
Cc: pavel@kernel.org, linux-kernel@vger.kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, linux-leds@vger.kernel.org,
linux-doc@vger.kernel.org, wse@tuxedocomputers.com,
jacek.anaszewski@gmail.com, pobrn@protonmail.com,
m.tretter@pengutronix.de
Subject: Re: (subset) [PATCH v4 1/1] leds: Introduce the multi_max_intensity sysfs attribute
Date: Tue, 26 May 2026 18:09:08 +0100 [thread overview]
Message-ID: <20260526170908.GJ3591266@google.com> (raw)
In-Reply-To: <b04d64b7-1a50-4b3d-95f3-2bcb502c0a5b@gmx.de>
On Sat, 23 May 2026, Armin Wolf wrote:
> Am 20.05.26 um 16:34 schrieb Lee Jones:
>
> > On Sat, 09 May 2026 23:46:03 +0200, Armin Wolf wrote:
> > > Some multicolor LEDs support global brightness control in hardware,
> > > meaning that the maximum intensity of the color components is not
> > > connected to the maximum global brightness. Such LEDs cannot be
> > > described properly by the current multicolor LED class interface,
> > > because it assumes that the maximum intensity of each color component
> > > is described by the maximum global brightness of the LED.
> > >
> > > [...]
> > Applied, thanks!
> >
> > [1/1] leds: Introduce the multi_max_intensity sysfs attribute
> > commit: b1a9b7a904af2c793850f83a4801a013a718fc47
>
> Thank you :)
>
> I just noticed that i forgot to update the Date field inside the sysfs documentation, it should
> have been:
>
> Date: May 2026
> KernelVersion: 7.2
>
> Should i send a separate patch for this or can you edit the patch inplace?
Subsequent patch please.
--
Lee Jones
prev parent reply other threads:[~2026-05-26 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 21:46 [PATCH v4 0/1] leds: Introduce the multi_max_intensity sysfs attribute Armin Wolf
2026-05-09 21:46 ` [PATCH v4 1/1] " Armin Wolf
2026-05-20 14:34 ` (subset) " Lee Jones
2026-05-22 22:05 ` Armin Wolf
2026-05-26 17:09 ` 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=20260526170908.GJ3591266@google.com \
--to=lee@kernel.org \
--cc=W_Armin@gmx.de \
--cc=corbet@lwn.net \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=pavel@kernel.org \
--cc=pobrn@protonmail.com \
--cc=skhan@linuxfoundation.org \
--cc=wse@tuxedocomputers.com \
/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