From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] doc: add link to sparse's home page/internal docs
Date: Sun, 28 Jun 2020 11:50:34 +0200 [thread overview]
Message-ID: <20200628095034.69520-1-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20200626112349.1292a654@lwn.net>
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>
---
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 6f4870528226..e20b8b8b78ed 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.kernl.org.
Using sparse for typechecking
--
2.27.0
next prev parent reply other threads:[~2020-06-28 9:50 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 ` Luc Van Oostenryck [this message]
2020-06-29 4:41 ` [PATCH] doc: add link to sparse's home page/internal docs 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
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=20200628095034.69520-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.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
all inboxes | Powered by JetHome®