From: Guenter Roeck <linux@roeck-us.net>
To: Kousik Sanagavarapu <five231003@gmail.com>
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: Wed, 20 Mar 2024 10:57:37 -0700 [thread overview]
Message-ID: <6f5f3110-355e-4933-840d-735b90d53ee6@roeck-us.net> (raw)
In-Reply-To: <20240318154540.90613-3-five231003@gmail.com>
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
> Instruments since 2011 and hence http://www.national.com/ doesn't work
> anymore.
>
> Fixes: e1a8e913f97e ("[PATCH] lm70: New hardware monitoring driver")
> Signed-off-by: Kousik Sanagavarapu <five231003@gmail.com>
Applied to hwmon-next.
Please note that I'll push the branch after the commit window closed.
Thanks,
Guenter
next prev parent reply other threads:[~2024-03-20 17:57 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
2024-03-18 18:55 ` Guenter Roeck
2024-03-20 17:57 ` Guenter Roeck [this message]
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=6f5f3110-355e-4933-840d-735b90d53ee6@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=five231003@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.