From: Laveesh Bansal <laveeshb@laveeshbansal•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Guenter Roeck <linux@roeck-us•net>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
linux-hwmon@vger•kernel.org,
Laveesh Bansal <laveeshb@laveeshbansal•com>
Subject: [PATCH] Documentation: hwmon: coretemp: Fix malformed RST table
Date: Tue, 13 Jan 2026 05:54:25 +0000 [thread overview]
Message-ID: <20260113055425.966495-1-laveeshb@laveeshbansal.com> (raw)
In-Reply-To: <20260113155444.57c7775b@canb.auug.org.au>
Widen the processor column in the TjMax table to accommodate longer
entries like "Celeron/Pentium Processors (Goldmont Plus/Gemini Lake)"
which exceed the previous 47-character column width.
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>
---
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..a3943656fab6 100644
--- a/Documentation/hwmon/coretemp.rst
+++ b/Documentation/hwmon/coretemp.rst
@@ -69,8 +69,8 @@ for your CPU, you can pass the correct TjMax value as a module parameter
Appendix A. Known TjMax lists (TBD):
Some information comes from ark.intel.com
-=============== =============================================== ================
-Process Processor TjMax(C)
+=============== ======================================================= ================
+Process Processor TjMax(C)
22nm Core i5/i7 Processors
i7 3920XM, 3820QM, 3720QM, 3667U, 3520M 105
@@ -228,4 +228,4 @@ Process Processor TjMax(C)
65nm Celeron Processors
T1700/1600 100
560/550/540/530 100
-=============== =============================================== ================
+=============== ======================================================= ================
--
2.43.0
next prev parent reply other threads:[~2026-01-13 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 4:54 linux-next: build warning after merge of the hwmon-staging tree Stephen Rothwell
2026-01-13 5:54 ` Laveesh Bansal [this message]
2026-01-13 6:48 ` [PATCH] Documentation: hwmon: coretemp: Fix malformed RST table 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=20260113055425.966495-1-laveeshb@laveeshbansal.com \
--to=laveeshb@laveeshbansal$(echo .)com \
--cc=linux-hwmon@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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