From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 6/7] doc: use shorter titles
Date: Mon, 10 Aug 2020 23:53:35 +0200 [thread overview]
Message-ID: <20200810215336.76070-7-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20200810215336.76070-1-luc.vanoostenryck@gmail.com>
Mainly it's removing 'sparse' from the title.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
Documentation/IR.rst | 4 ++--
Documentation/dev-options.rst | 4 ++--
Documentation/doc-guide.rst | 4 ++--
Documentation/types.rst | 6 +++---
4 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/IR.rst b/Documentation/IR.rst
index 33a761662fad..97d4b2b27ee3 100644
--- a/Documentation/IR.rst
+++ b/Documentation/IR.rst
@@ -1,7 +1,7 @@
.. default-domain:: ir
-Sparse's Intermediate Representation
-====================================
+Intermediate Representation
+===========================
Instructions
~~~~~~~~~~~~
diff --git a/Documentation/dev-options.rst b/Documentation/dev-options.rst
index 23e8096c2cd0..57f9e8d6c4de 100644
--- a/Documentation/dev-options.rst
+++ b/Documentation/dev-options.rst
@@ -1,5 +1,5 @@
-sparse - extra options for developers
-=====================================
+Extra options for developers
+============================
SYNOPSIS
--------
diff --git a/Documentation/doc-guide.rst b/Documentation/doc-guide.rst
index 8133cb3a59df..29f39aab360a 100644
--- a/Documentation/doc-guide.rst
+++ b/Documentation/doc-guide.rst
@@ -1,5 +1,5 @@
-How to write sparse documentation
-=================================
+Documentation guide
+===================
Introduction
------------
diff --git a/Documentation/types.rst b/Documentation/types.rst
index 272f32a0f4ed..974f9861afef 100644
--- a/Documentation/types.rst
+++ b/Documentation/types.rst
@@ -1,6 +1,6 @@
-********************
-Sparse's Type System
-********************
+***********
+Type System
+***********
struct symbol is used to represent symbols & types but
most parts pertaining to the types are in the field 'ctype'.
--
2.28.0
next prev parent reply other threads:[~2020-08-10 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 21:53 [PATCH 0/7] doc: small tweaks to the online documentation Luc Van Oostenryck
2020-08-10 21:53 ` [PATCH 1/7] doc: use a smaller logo in the sidebar Luc Van Oostenryck
2020-08-10 21:53 ` [PATCH 2/7] doc: make the sidebar more compact Luc Van Oostenryck
2020-08-10 21:53 ` [PATCH 3/7] doc: decrease vertical spacing Luc Van Oostenryck
2020-08-10 21:53 ` [PATCH 4/7] doc: move down info about tarballs, after git repositories Luc Van Oostenryck
2020-08-10 21:53 ` [PATCH 5/7] doc: reorganize the table of content Luc Van Oostenryck
2020-08-10 21:53 ` Luc Van Oostenryck [this message]
2020-08-10 21:53 ` [PATCH 7/7] doc: add links to some external doc Luc Van Oostenryck
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=20200810215336.76070-7-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@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).