From: Ankan Biswas <spyjetfayed@gmail.com>
To: linux@roeck-us.net, corbet@lwn.net
Cc: skhan@linuxfoundation.org, khalid@kernel.org,
david.hunter.linux@gmail.com, linux-hwmon@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
Ankan Biswas <spyjetfayed@gmail.com>
Subject: [PATCH 0/3] docs/hwmon: Fix broken and missing Maxim chip links
Date: Fri, 17 Oct 2025 16:27:15 +0530 [thread overview]
Message-ID: <20251017105740.17646-1-spyjetfayed@gmail.com> (raw)
This patch series fixes broken or missing links related to Maxim chips in several
hwmon documentation files. And updates a the links that get redirected to analog.com
to their analog.com links.
These changes remove several warnings generated by `make linkcheckdocs`.
Patches are independent and touch multiple hwmon documentation files.
Ankan Biswas (3):
docs/hwmon: Fix broken maxim-ic.com links to analog.com
docs/hwmon: Add missing datasheet links for Maxim chips
docs/hwmon: Update maxim-ic.com links to analog.com
Documentation/hwmon/ds1621.rst | 20 ++++++++++++----
Documentation/hwmon/jc42.rst | 6 ++---
Documentation/hwmon/lm75.rst | 13 +++++++----
Documentation/hwmon/max127.rst | 4 +++-
Documentation/hwmon/max15301.rst | 8 +++++--
Documentation/hwmon/max16064.rst | 2 +-
Documentation/hwmon/max16065.rst | 16 ++++++-------
Documentation/hwmon/max1619.rst | 4 ++--
Documentation/hwmon/max16601.rst | 4 +++-
Documentation/hwmon/max1668.rst | 4 +++-
Documentation/hwmon/max197.rst | 8 +++++--
Documentation/hwmon/max20730.rst | 16 +++++++++----
Documentation/hwmon/max31722.rst | 8 +++++--
Documentation/hwmon/max31730.rst | 4 +++-
Documentation/hwmon/max31785.rst | 4 +++-
Documentation/hwmon/max31790.rst | 4 +++-
Documentation/hwmon/max31827.rst | 5 ++++
Documentation/hwmon/max34440.rst | 24 ++++++++++++++-----
Documentation/hwmon/max6620.rst | 4 +++-
Documentation/hwmon/max6639.rst | 4 +++-
Documentation/hwmon/max6650.rst | 8 +++++--
Documentation/hwmon/max6697.rst | 40 ++++++++++++++++++++++++--------
Documentation/hwmon/max77705.rst | 4 +++-
Documentation/hwmon/max8688.rst | 4 +++-
Documentation/hwmon/pmbus.rst | 4 ++--
25 files changed, 158 insertions(+), 64 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-17 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 10:57 Ankan Biswas [this message]
2025-10-17 10:57 ` [PATCH 1/3] docs/hwmon: Fix broken maxim-ic.com links to analog.com Ankan Biswas
2025-10-17 12:48 ` Guenter Roeck
2025-10-17 10:57 ` [PATCH 2/3] docs/hwmon: Add missing datasheet links for Maxim chips Ankan Biswas
2025-10-17 12:52 ` Guenter Roeck
2025-10-17 14:54 ` Ankan Biswas
2025-10-17 10:57 ` [PATCH 3/3] docs/hwmon: Update maxim-ic.com links to analog.com Ankan Biswas
2025-10-17 12:53 ` Guenter Roeck
2025-10-17 15:47 ` [PATCH v2 1/3] Fix broken " Ankan Biswas
2025-10-18 12:49 ` Guenter Roeck
2025-10-17 16:08 ` [PATCH v2 2/3] Add missing datasheet links for Maxim chips Ankan Biswas
2025-10-18 12:50 ` Guenter Roeck
2025-10-17 16:34 ` [PATCH v2 3/3] Update maxim-ic.com links to analog.com Ankan Biswas
2025-10-18 12:51 ` 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=20251017105740.17646-1-spyjetfayed@gmail.com \
--to=spyjetfayed@gmail.com \
--cc=corbet@lwn.net \
--cc=david.hunter.linux@gmail.com \
--cc=khalid@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).