From: Lee Jones <lee@kernel.org>
To: "Björn Persson" <Bjorn@xn--rombobjrn-67a.se>
Cc: Pavel Machek <pavel@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-leds@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: leds: uleds: Make the documentation match the code.
Date: Thu, 23 Apr 2026 16:26:55 +0100 [thread overview]
Message-ID: <20260423152655.GF170138@google.com> (raw)
In-Reply-To: <20260402220811.4804DD8F722@tag.xn--rombobjrn-67a.se>
On Thu, 02 Apr 2026, Björn Persson wrote:
> From: Björn Persson <Bjorn@Rombobjörn.se>
>
> · max_brightness must be set. Leaving it uninitialized or just omitting it
> won't work.
What are these points? How do you even type one of those?
Anyway, proper sentences / paragraphs is better.
> · The maximum brightness is not 255 but the value given to max_brightness.
>
> · Brightness values must be read as ints, not bytes.
>
> · The ints are signed, so the word "unsigned" is misleading.
>
> Signed-off-by: Björn Persson <Bjorn@Rombobjörn.se>
> ---
> Documentation/leds/uleds.rst | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/leds/uleds.rst b/Documentation/leds/uleds.rst
> index 83221098009c..9875a0fa4185 100644
> --- a/Documentation/leds/uleds.rst
> +++ b/Documentation/leds/uleds.rst
> @@ -17,16 +17,20 @@ structure to it (found in kernel public header file linux/uleds.h)::
>
> struct uleds_user_dev {
> char name[LED_MAX_NAME_SIZE];
> + int max_brightness;
> };
>
> -A new LED class device will be created with the name given. The name can be
> -any valid sysfs device node name, but consider using the LED class naming
> -convention of "devicename:color:function".
> +A new LED class device will be created with the given name and maximum
Did you mean to revers "name given"? A "given name" usually means
something else.
> +brightness. The name can be any valid sysfs device node name, but consider
> +using the LED class naming convention of "devicename:color:function".
>
> -The current brightness is found by reading a single byte from the character
> -device. Values are unsigned: 0 to 255. Reading will block until the brightness
> -changes. The device node can also be polled to notify when the brightness value
> -changes.
> +Although max_brightness is a signed int, only positive values are valid:
> +1 to INT_MAX.
What about 0?
> +The current brightness is found by reading a whole int from the character
Try not to shorten names in documentation "integer".
Why do we need to specify "whole"?
> +device. The possible values are 0 to max_brightness. Reading will block until
> +the brightness changes. The device node can also be polled to notify when the
> +brightness value changes.
>
> The LED class device will be removed when the open file handle to /dev/uleds
> is closed.
> --
> 2.53.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-04-23 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 20:27 [PATCH] docs: leds: uleds: Make the documentation match the code Björn Persson
2026-04-23 15:26 ` Lee Jones [this message]
2026-04-24 17:47 ` Björn Persson
2026-05-07 13:11 ` Lee Jones
2026-05-10 19:43 ` Björn Persson
2026-05-13 13:45 ` 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=20260423152655.GF170138@google.com \
--to=lee@kernel.org \
--cc=Bjorn@xn--rombobjrn-67a.se \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=skhan@linuxfoundation.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.