From: Kousik Sanagavarapu <five231003@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-hwmon@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH v2 2/2] hwmon: lm70: fix links in doc and comments
Date: Mon, 18 Mar 2024 23:59:55 +0530 [thread overview]
Message-ID: <ZfiII_4xMnemzWqi@five231003> (raw)
In-Reply-To: <6c8b2699-5488-4ae0-8d78-59bcb2030a2e@roeck-us.net>
On Mon, Mar 18, 2024 at 11:11:29AM -0700, Guenter Roeck wrote:
> On Mon, Mar 18, 2024 at 09:08:35PM +0530, Kousik Sanagavarapu wrote:
> > Update links in the documentation and in-code comments which point to
> > the datasheet.
> >
> > The current links don't work because National Semiconductor (which is
> > the manufacturer of this board and lm70) has been a part of Texas
> ^^^^^^^^^^
>
> Is this a leftover from the other patch ? The lm70 driver supports
> the LM70 chip, not a specific board.
Yeah, it should be "the manufacturer of lm70". Thanks for spotting.
Should I fix and resend this specific patch as v3 or would you edit it
while pulling?
next prev parent reply other threads:[~2024-03-18 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 13:04 [PATCH] spi: lm70llp: fix links in doc Kousik Sanagavarapu
2024-03-18 15:38 ` [PATCH v2 0/2] lm70 and lm70llp doc link fixes Kousik Sanagavarapu
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 [this message]
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=ZfiII_4xMnemzWqi@five231003 \
--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