From: Vitor Massaru Iha <vitor@massaru.org>
To: linux-doc@vger.kernel.org
Cc: martin@omnibond.com, corbet@lwn.net, brendanhiggins@google.com,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
devel@lists.orangefs.org, hubcap@omnibond.com
Subject: [Linux-kernel-mentees] [PATCH] docs: filesystems: fix `make htmldocs` warning
Date: Thu, 30 Apr 2020 16:07:37 -0300 [thread overview]
Message-ID: <20200430190737.80950-1-vitor@massaru.org> (raw)
make htmldocs
Documentation/filesystems/orangefs.rst:124: WARNING: Literal block expected; none found.
Signed-off-by: Vitor Massaru Iha <vitor@massaru.org>
---
Documentation/filesystems/orangefs.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/filesystems/orangefs.rst b/Documentation/filesystems/orangefs.rst
index e41369709c5b..628dc220567e 100644
--- a/Documentation/filesystems/orangefs.rst
+++ b/Documentation/filesystems/orangefs.rst
@@ -119,9 +119,7 @@ it comes to that question::
/opt/ofs/bin/pvfs2-genconfig /etc/pvfs2.conf
-Create an /etc/pvfs2tab file::
-
-Localhost is fine for your pvfs2tab file:
+Create an /etc/pvfs2tab file. Localhost is fine for your pvfs2tab file::
echo tcp://localhost:3334/orangefs /pvfsmnt pvfs2 defaults,noauto 0 0 > \
/etc/pvfs2tab
--
2.25.1
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next reply other threads:[~2020-04-30 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 19:07 Vitor Massaru Iha [this message]
2020-04-30 19:47 ` [Linux-kernel-mentees] [PATCH] docs: filesystems: fix `make htmldocs` warning Jonathan Corbet
2020-04-30 19:57 ` Vitor Massaru Iha
2020-04-30 20:04 ` Jonathan Corbet
2020-04-30 20:08 ` Vitor Massaru Iha
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=20200430190737.80950-1-vitor@massaru.org \
--to=vitor@massaru.org \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=devel@lists.orangefs.org \
--cc=hubcap@omnibond.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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).