From: Johan Hovold <johan@kernel.org>
To: Sanjeev Gupta <ghane0@gmail.com>
Cc: corbet@lwn.net, gregkh@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/usb: Fix dead links and convert others to https
Date: Thu, 29 Mar 2018 12:02:55 +0200 [thread overview]
Message-ID: <20180329100255.GA16578@localhost> (raw)
In-Reply-To: <20180328160752.17840-1-ghane0@gmail.com>
On Thu, Mar 29, 2018 at 12:07:52AM +0800, Sanjeev Gupta wrote:
> All links checked, for those dead, I have replaced with copies on
> archive.org. For some, https is not supported, http has been
> kept.
>
> The git log says this was last done by Justin P. Mattock in 2010.
> Hi, Justin!
Not sure this belongs in the commit message (and did you forget to CC
Justin?).
> Signed-off-by: Sanjeev Gupta <ghane0@gmail.com>
> ---
> Documentation/usb/usb-serial.txt | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
> For any questions or problems with this driver, please contact Hugh
> Blemings at hugh@misc.nu
> @@ -436,7 +437,8 @@ Winchiphead CH341 Driver
> also implements an IEEE 1284 parallel port, I2C and SPI, but that is not
> supported by the driver. The protocol was analyzed from the behaviour
> of the Windows driver, no datasheet is available at present.
> - The manufacturer's website: http://www.winchiphead.com/.
> + The manufacturer's website:
> + https://web.archive.org/web/20170911133726/http://winchiphead.com/ .
AFAICT this link is still working.
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-03-29 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 16:07 [PATCH] Documentation/usb: Fix dead links and convert others to https Sanjeev Gupta
2018-03-29 10:02 ` Johan Hovold [this message]
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=20180329100255.GA16578@localhost \
--to=johan@kernel.org \
--cc=corbet@lwn.net \
--cc=ghane0@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).