From: Laveesh Bansal <laveeshb@laveeshbansal.com>
To: linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org
Cc: linux@roeck-us.net, corbet@lwn.net, rdunlap@infradead.org,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org,
Laveesh Bansal <laveeshb@laveeshbansal.com>
Subject: [PATCH v2] Documentation: hwmon: coretemp: Fix malformed RST table
Date: Tue, 13 Jan 2026 07:53:22 +0000 [thread overview]
Message-ID: <20260113075322.978737-1-laveeshb@laveeshbansal.com> (raw)
Shorten the Celeron/Pentium processor entries in the TjMax table to fit
within the 47-character column width, fixing the RST table parsing error.
The following entries exceeded the column width:
- "Celeron/Pentium Processors (Goldmont/Apollo Lake)" (49 chars)
- "Celeron/Pentium Processors (Goldmont Plus/Gemini Lake)" (54 chars)
- "Celeron/Pentium Processors (Tremont/Jasper Lake)" (48 chars)
Drop "Processors" from these entries as this preserves all searchable
technical keywords (Celeron, Pentium, Goldmont, Gemini Lake, etc.) while
"Processors" is implied by the chip names and adds no search value.
Fixes: 099cc1051df7 ("Documentation: hwmon: coretemp: Update supported CPUs and TjMax values")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20260113155444.57c7775b@canb.auug.org.au/
Signed-off-by: Laveesh Bansal <laveeshb@laveeshbansal.com>
---
v2:
- Shorten text instead of widening columns (widening would require
adjusting 101 data rows to realign TjMax values)
Tested with:
- python3 -m docutils Documentation/hwmon/coretemp.rst /dev/null
- make htmldocs
Open to alternative approaches if anyone has a better solution.
---
Documentation/hwmon/coretemp.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/hwmon/coretemp.rst b/Documentation/hwmon/coretemp.rst
index 3afb179e0ced..3ba44b57d028 100644
--- a/Documentation/hwmon/coretemp.rst
+++ b/Documentation/hwmon/coretemp.rst
@@ -120,12 +120,12 @@ Process Processor TjMax(C)
x5-E3940/E3930 105
x7-E3950 105
-14nm Celeron/Pentium Processors (Goldmont/Apollo Lake)
+14nm Celeron/Pentium (Goldmont/Apollo Lake)
J3455/J3355 105
N3450/N3350 105
N4200 105
-14nm Celeron/Pentium Processors (Goldmont Plus/Gemini Lake)
+14nm Celeron/Pentium (Goldmont Plus/Gemini Lake)
J4105/J4005 105
N4100/N4000 105
N5000 105
@@ -133,7 +133,7 @@ Process Processor TjMax(C)
10nm Atom Processors (Tremont/Elkhart Lake)
x6000E 105
-10nm Celeron/Pentium Processors (Tremont/Jasper Lake)
+10nm Celeron/Pentium (Tremont/Jasper Lake)
N4500/N5100/N6000 series 105
45nm Xeon Processors 5400 Quad-Core
--
2.43.0
next reply other threads:[~2026-01-13 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 7:53 Laveesh Bansal [this message]
2026-01-13 14:52 ` Guenter Roeck
2026-01-13 16:19 ` Randy Dunlap
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=20260113075322.978737-1-laveeshb@laveeshbansal.com \
--to=laveeshb@laveeshbansal.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®