linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-mtd@lists.infradead.org
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	"Richard Weinberger" <richard@nod.at>,
	"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	"Miklos Szeredi" <mszeredi@redhat.com>,
	"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
	"Jaskaran Singh" <jaskaransingh7654321@gmail.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Tobin C. Harding" <tobin@kernel.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Rob Herring" <robh@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/2] docs: ubifs-authentication: Add a top-level heading
Date: Sat,  5 Sep 2020 22:43:26 +0200	[thread overview]
Message-ID: <20200905204326.1378339-3-j.neuschaefer@gmx.net> (raw)
In-Reply-To: <20200905204326.1378339-1-j.neuschaefer@gmx.net>

This prevents the chapter headings from showing up in the table of
contents in filesystems/index.html.

Note that I didn't pick "UBIFS Authentication" as the document title,
because there is a chapter of the same name, and Sphinx complains about
multiple headings with the same name:

  /.../Documentation/filesystems/ubifs-authentication.rst:207:
  WARNING: duplicate label filesystems/ubifs-authentication:ubifs
  authentication, other instance in
  /.../Documentation/filesystems/ubifs-authentication.rst

Remove the :orphan: tag, as the document has been included into the
toctree.

Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
---
 Documentation/filesystems/ubifs-authentication.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/filesystems/ubifs-authentication.rst b/Documentation/filesystems/ubifs-authentication.rst
index 1f39c8cea7029..5210aed2afbc3 100644
--- a/Documentation/filesystems/ubifs-authentication.rst
+++ b/Documentation/filesystems/ubifs-authentication.rst
@@ -1,11 +1,13 @@
 .. SPDX-License-Identifier: GPL-2.0

-:orphan:
-
 .. UBIFS Authentication
 .. sigma star gmbh
 .. 2018

+============================
+UBIFS Authentication Support
+============================
+
 Introduction
 ============

--
2.28.0


  parent reply	other threads:[~2020-09-05 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 20:43 [PATCH v2 0/2] ubifs: Fixes around ubifs-authentication.rst Jonathan Neuschäfer
2020-09-05 20:43 ` [PATCH v2 1/2] MAINTAINERS: Add ubifs-authentication.rst to UBIFS Jonathan Neuschäfer
2020-09-05 20:43 ` Jonathan Neuschäfer [this message]
2020-09-09 17:53 ` [PATCH v2 0/2] ubifs: Fixes around ubifs-authentication.rst 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=20200905204326.1378339-3-j.neuschaefer@gmx.net \
    --to=j.neuschaefer@gmx.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dwlsalmeida@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jaskaransingh7654321@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=stefanha@redhat.com \
    --cc=tobin@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).