From: Kousik Sanagavarapu <five231003@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-spi@vger.kernel.org, linux-hwmon@vger.kernel.org,
Mark Brown <broonie@kernel.org>, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Kousik Sanagavarapu <five231003@gmail.com>
Subject: [PATCH v2 0/2] lm70 and lm70llp doc link fixes
Date: Mon, 18 Mar 2024 21:08:33 +0530 [thread overview]
Message-ID: <20240318154540.90613-1-five231003@gmail.com> (raw)
In-Reply-To: <20240318130840.74589-1-five231003@gmail.com>
Fix links from the documentation and in-code comments pointing to
datasheets.
Changes since v1:
- I forgot to fix the links in in-code comments in spi, so do that.
- New commit to address the same issues in hwmon/lm70 since the spi eval board
is based on that.
Sorry for the noise from v1.
Kousik Sanagavarapu (2):
spi: lm70llp: fix links in doc and comments
hwmon: lm70: fix links in doc and comments
Documentation/hwmon/lm70.rst | 2 +-
Documentation/spi/spi-lm70llp.rst | 4 ++--
drivers/hwmon/lm70.c | 4 ++--
drivers/spi/spi-lm70llp.c | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
--
2.44.0.273.g4bc5b65358.dirty
next parent reply other threads:[~2024-03-18 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318130840.74589-1-five231003@gmail.com>
2024-03-18 15:38 ` Kousik Sanagavarapu [this message]
2024-03-18 15:38 ` [PATCH v2 1/2] spi: lm70llp: fix links in doc and comments Kousik Sanagavarapu
2024-03-18 15:38 ` [PATCH v2 2/2] hwmon: lm70: " Kousik Sanagavarapu
2024-03-18 18:11 ` Guenter Roeck
2024-03-18 18:29 ` Kousik Sanagavarapu
2024-03-18 18:55 ` Guenter Roeck
2024-03-20 17:57 ` Guenter Roeck
2024-03-18 17:27 ` (subset) [PATCH v2 0/2] lm70 and lm70llp doc link fixes Mark Brown
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=20240318154540.90613-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=broonie@kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 read-only IMAP folder(s) and NNTP newsgroup(s).