From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Abhinav Saxena <xandfury@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] docs: hwmon: Fix typos in sch5627 and max31827
Date: Sat, 9 Nov 2024 06:57:40 +0700 [thread overview]
Message-ID: <Zy6ldOPnnl5ocf6V@archie.me> (raw)
In-Reply-To: <20241108212201.144482-1-xandfury@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
On Fri, Nov 08, 2024 at 02:22:01PM -0700, Abhinav Saxena wrote:
> diff --git a/Documentation/hwmon/max31827.rst b/Documentation/hwmon/max31827.rst
> index 9c11a9518c67..6cc5088b26b7 100644
> --- a/Documentation/hwmon/max31827.rst
> +++ b/Documentation/hwmon/max31827.rst
> @@ -136,7 +136,7 @@ PEC Support
>
> When reading a register value, the PEC byte is computed and sent by the chip.
>
> -PEC on word data transaction respresents a signifcant increase in bandwitdh
> +PEC on word data transaction represents a significant increase in bandwidth
> usage (+33% for both write and reads) in normal conditions.
>
> Since this operation implies there will be an extra delay to each
> diff --git a/Documentation/hwmon/sch5627.rst b/Documentation/hwmon/sch5627.rst
> index 8639dff234fc..5f521c6e90ab 100644
> --- a/Documentation/hwmon/sch5627.rst
> +++ b/Documentation/hwmon/sch5627.rst
> @@ -39,7 +39,7 @@ Controlling fan speed
> ---------------------
>
> The SCH5627 allows for partially controlling the fan speed. If a temperature
> -channel excedes tempX_max, all fans are forced to maximum speed. The same is not
> +channel exceeds tempX_max, all fans are forced to maximum speed. The same is not
> true for tempX_crit, presumably some other measures to cool down the system are
> take in this case.
> In which way the value of fanX_min affects the fan speed is currently unknown.
Looks OK, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-08 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 21:22 [PATCH] docs: hwmon: Fix typos in sch5627 and max31827 Abhinav Saxena
2024-11-08 22:29 ` Randy Dunlap
2024-11-08 23:57 ` Bagas Sanjaya [this message]
2024-11-09 16:19 ` Guenter Roeck
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=Zy6ldOPnnl5ocf6V@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=xandfury@gmail.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