All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/5] Documentation: update URL for Michael K. Johnson's articles
Date: Thu, 31 Mar 2016 00:50:17 -0600	[thread overview]
Message-ID: <20160331005017.78fa5dc2@lwn.net> (raw)
In-Reply-To: <1458391884-21795-2-git-send-email-luisbg@osg.samsung.com>

On Sat, 19 Mar 2016 12:51:21 +0000
Luis de Bethencourt <luisbg@osg.samsung.com> wrote:

> The URL for "Writing Linux Device Drivers" hasn't been available in some
> time. Updating it to the URL of Michael K. Johnson's "Linux Kernel Hackers'
> Guide"

But that's a different work, I don't think it makes sense to just
substitute in the URL.  It would be better, I think, to turn this into an
entry for the KHG if we really want that.

Thanks,

jon

  parent reply	other threads:[~2016-03-31  6:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-19 12:51 [PATCH 1/5] Documentation: add Linux Kernel Development book Luis de Bethencourt
2016-03-19 12:51 ` [PATCH 2/5] Documentation: update URL for Michael K. Johnson's articles Luis de Bethencourt
2016-03-19 13:00   ` Luis de Bethencourt
2016-03-31  6:50   ` Jonathan Corbet [this message]
2016-03-19 12:51 ` [PATCH 3/5] Documentation: update URL of Analysis of the Ext2fs structure Luis de Bethencourt
2016-03-31  6:51   ` Jonathan Corbet
2016-03-19 12:51 ` [PATCH 4/5] Documentation: update URLs for Richard Gooch's articles Luis de Bethencourt
2016-03-31  6:51   ` Jonathan Corbet
2016-03-19 12:51 ` [PATCH 5/5] Documentation: update URL for Porting Linux 2.0 Drivers to 2.2 Luis de Bethencourt
2016-03-31  6:52   ` Jonathan Corbet
2016-03-31 10:50     ` Luis de Bethencourt
2016-03-31  6:49 ` [PATCH 1/5] Documentation: add Linux Kernel Development book Jonathan Corbet

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=20160331005017.78fa5dc2@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    /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.