From: Randy Dunlap <rdunlap@infradead.org>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Cc: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Subject: [PATCH] Documentation: fuse: fix Sphinx directive warning
Date: Sun, 9 Feb 2020 19:33:53 -0800 [thread overview]
Message-ID: <1f114330-bd67-bc07-912e-90432786b6b4@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix a documentation warning due to missing a blank line after a directive:
Documentation/filesystems/fuse.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Cc: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
---
Documentation/filesystems/fuse.rst | 1 +
1 file changed, 1 insertion(+)
--- lnx-56-rc1.orig/Documentation/filesystems/fuse.rst
+++ lnx-56-rc1/Documentation/filesystems/fuse.rst
@@ -1,4 +1,5 @@
.. SPDX-License-Identifier: GPL-2.0
+
==============
FUSE
==============
reply other threads:[~2020-02-10 3:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1f114330-bd67-bc07-912e-90432786b6b4@infradead.org \
--to=rdunlap@infradead.org \
--cc=dwlsalmeida@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).