From: Randy Dunlap <rdunlap@infradead.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: hwmon: sysfs-interface: Fix bracket
Date: Thu, 3 Sep 2026 09:30:42 -0700 [thread overview]
Message-ID: <626e7372-352e-4339-8e3d-022bdb1b2625@infradead.org> (raw)
In-Reply-To: <20260903161204.735276-2-manuelebnerli@mailbox.org>
On 9/3/26 9:12 AM, Manuel Ebner wrote:
> Add missing ')'.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/hwmon/sysfs-interface.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/hwmon/sysfs-interface.rst b/Documentation/hwmon/sysfs-interface.rst
> index 94e1bbce1..7cf4178c3 100644
> --- a/Documentation/hwmon/sysfs-interface.rst
> +++ b/Documentation/hwmon/sysfs-interface.rst
> @@ -47,7 +47,7 @@ There is only one value per file, unlike the older /proc specification.
> The common scheme for files naming is: <type><number>_<item>. Usual
> types for sensor chips are "in" (voltage), "temp" (temperature) and
> "fan" (fan). Usual items are "input" (measured value), "max" (high
> -threshold, "min" (low threshold). Numbering usually starts from 1,
> +threshold), "min" (low threshold). Numbering usually starts from 1,
> except for voltages which start from 0 (because most data sheets use
> this). A number is always used for elements that can be present more
> than once, even if there is a single element of the given type on the
--
~Randy
prev parent reply other threads:[~2026-09-03 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 16:12 [PATCH] docs: hwmon: sysfs-interface: Fix bracket Manuel Ebner
2026-09-03 16:30 ` Randy Dunlap [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=626e7372-352e-4339-8e3d-022bdb1b2625@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=manuelebnerli@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox