linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v2] doc: add link to sparse's home page/internal docs
Date: Sun, 5 Jul 2020 14:33:42 -0600	[thread overview]
Message-ID: <20200705143342.0d083b59@lwn.net> (raw)
In-Reply-To: <20200629161310.89783-1-luc.vanoostenryck@gmail.com>

On Mon, 29 Jun 2020 18:13:10 +0200
Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote:

> Sparse's home page used to be a wiki (sparse.wiki.kernel.org)
> but this wiki only contained a short intro and the release notes.
> But nowadays, sparse's main page is sparse.docs.kernel.org,
> which contains all what was in the wiki but also other documentation,
> mainly oriented about sparse's internals.
> 
> So, add a link to this in the kernel documentation.
> 
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
> 
> Changes since v1:
> * fix a typo (s/kernl/kernel/) thanks to Mike Rapoport.
> 
>  Documentation/dev-tools/sparse.rst | 2 ++
>  1 file changed, 2 insertions(+)

When I answered saying I'd applied the v1 patch, I meant I'd really
applied this one, of course...sorry for the noise.

jon

  parent reply	other threads:[~2020-07-05 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200626112349.1292a654@lwn.net>
2020-06-28  9:50 ` [PATCH] doc: add link to sparse's home page/internal docs Luc Van Oostenryck
2020-06-29  4:41   ` Mike Rapoport
2020-06-29 16:13     ` [PATCH v2] " Luc Van Oostenryck
2020-06-29 20:05       ` Mike Rapoport
2020-07-05 20:33       ` Jonathan Corbet [this message]
2020-07-05 20:30   ` [PATCH] " 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=20200705143342.0d083b59@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=rppt@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).