From: sashiko-bot@kernel.org
To: "Ximing Zhang" <xzhangjr@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: coretemp: Fix documentation wording
Date: Tue, 16 Jun 2026 12:10:01 +0000 [thread overview]
Message-ID: <20260616121001.939E11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260616120643.29079-1-xzhangjr@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incorrect capitalization introduced in documentation fix.
--
commit 6d16e0e40567aa60f1f239fdc56d9c06e86611fa
Author: Ximing Zhang <xzhangjr@gmail.com>
hwmon: coretemp: Fix documentation wording
This commit fixes two minor wording issues in the coretemp documentation by
adding a missing article and correcting sysfs capitalization.
> diff --git a/Documentation/hwmon/coretemp.rst b/Documentation/hwmon/coretemp.rst
> index f63b21f24d42c..5ce125b0be2ed 100644
> --- a/Documentation/hwmon/coretemp.rst
> +++ b/Documentation/hwmon/coretemp.rst
> @@ -44,9 +44,9 @@ Temperature known as TjMax is the maximum junction temperature of processor,
> which depends on the CPU model. See table below. At this temperature, protection
> mechanism will perform actions to forcibly cool down the processor. Alarm
> may be raised, if the temperature grows enough (more than TjMax) to trigger
> -the Out-Of-Spec bit. Following table summarizes the exported sysfs files:
> +the Out-Of-Spec bit. The Following table summarizes the exported sysfs files:
[Severity: Low]
This isn't a bug, but the capitalization of "Following" was retained after
adding "The", resulting in the grammatically incorrect phrase "The Following
table".
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260616120643.29079-1-xzhangjr@gmail.com?part=1
prev parent reply other threads:[~2026-06-16 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 12:06 [PATCH] hwmon: coretemp: Fix documentation wording Ximing Zhang
2026-06-16 12:10 ` sashiko-bot [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=20260616121001.939E11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xzhangjr@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