From: Mike Rapoport <rppt@kernel.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] doc: add link to sparse's home page/internal docs
Date: Mon, 29 Jun 2020 23:05:09 +0300 [thread overview]
Message-ID: <20200629200509.GE1492837@kernel.org> (raw)
In-Reply-To: <20200629161310.89783-1-luc.vanoostenryck@gmail.com>
On Mon, Jun 29, 2020 at 06:13:10PM +0200, Luc Van Oostenryck 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>
Acked-by: Mike Rapoport <rppt@linux.ibm.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(+)
>
> diff --git a/Documentation/dev-tools/sparse.rst b/Documentation/dev-tools/sparse.rst
> index 8a7055593c31..02102be7ff49 100644
> --- a/Documentation/dev-tools/sparse.rst
> +++ b/Documentation/dev-tools/sparse.rst
> @@ -9,6 +9,8 @@ Sparse is a semantic checker for C programs; it can be used to find a
> number of potential problems with kernel code. See
> https://lwn.net/Articles/689907/ for an overview of sparse; this document
> contains some kernel-specific sparse information.
> +More information on sparse, mainly about its internals, can be found in
> +its official pages at https://sparse.docs.kernel.org.
>
>
> Using sparse for typechecking
> --
> 2.27.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2020-06-29 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 15:33 [PATCH] doc: update URL for sparse's tarballs Luc Van Oostenryck
2020-06-26 17:23 ` Jonathan Corbet
2020-06-28 9:49 ` Luc Van Oostenryck
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 [this message]
2020-07-05 20:33 ` Jonathan Corbet
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=20200629200509.GE1492837@kernel.org \
--to=rppt@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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 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).