From: Tommaso Merciai <tomm.merciai@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
arjan@linux.intel.com
Subject: Re: [PATCH] docs: update file link location
Date: Sun, 17 Oct 2021 09:27:24 +0200 [thread overview]
Message-ID: <20211017072724.GA3786@tom-desktop> (raw)
In-Reply-To: <87ee8quipd.fsf@meer.lwn.net>
On Tue, Oct 12, 2021 at 01:49:34PM -0600, Jonathan Corbet wrote:
> Tommaso Merciai <tomm.merciai@gmail.com> writes:
>
> [CC += Arjan just in case]
>
> > Fix web error: this site can't be reached
> >
> > Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> > ---
> > Documentation/process/submitting-drivers.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/submitting-drivers.rst b/Documentation/process/submitting-drivers.rst
> > index 3861887e0ca5..8413b693d10d 100644
> > --- a/Documentation/process/submitting-drivers.rst
> > +++ b/Documentation/process/submitting-drivers.rst
> > @@ -185,7 +185,7 @@ Linux USB project:
> > http://www.linux-usb.org/
> >
> > How to NOT write kernel driver by Arjan van de Ven:
> > - http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
> > + https://landley.net/kdocs/ols/2002/ols2002-pages-545-555.pdf
>
> This is an OK change, I guess...a working link is better than a broken
> one. That said, I do have to wonder whether this link needs to be
> preserved at all. That paper was good advice 19 years ago, but I'm not
> sure it has much to tell people in 2021; the days of having to tell
> developers to think about SMP systems are past.
Got it :)
Thanks,
tommaso
>
> I'll apply this for now, though.
>
> Thanks,
>
> jon
prev parent reply other threads:[~2021-10-17 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 22:07 [PATCH] docs: update file link location Tommaso Merciai
2021-10-12 19:49 ` Jonathan Corbet
2021-10-17 7:27 ` Tommaso Merciai [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=20211017072724.GA3786@tom-desktop \
--to=tomm.merciai@gmail.com \
--cc=arjan@linux.intel.com \
--cc=corbet@lwn.net \
--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).