From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: adobriyan@gmail.com, corbet@lwn.net, mchehab+huawei@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 1/2] doc: filesystems: proc: Remove stray '-' preventing table output
Date: Tue, 14 Jul 2020 21:06:43 +1200 [thread overview]
Message-ID: <20200714090644.13011-1-chris.packham@alliedtelesis.co.nz> (raw)
When processing proc.rst sphinx complained
Documentation/filesystems/proc.rst:548: WARNING: Malformed table.
Text in column margin in table line 29.
This caused the entire table to be dropped. Removing the stray '-'
resolves the error and produces the desired table.
Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
---
Documentation/filesystems/proc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 996f3cfe7030..53a0230a08e2 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -545,7 +545,7 @@ encoded manner. The codes are the following:
hg huge page advise flag
nh no huge page advise flag
mg mergable advise flag
- bt - arm64 BTI guarded page
+ bt arm64 BTI guarded page
== =======================================
Note that there is no guarantee that every flag and associated mnemonic will
--
2.27.0
next reply other threads:[~2020-07-14 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 9:06 Chris Packham [this message]
2020-07-14 9:06 ` [PATCH 2/2] doc: filesystems: proc: Fix literal blocks Chris Packham
2020-07-14 9:57 ` Mike Rapoport
2020-07-15 20:47 ` Chris Packham
2020-07-14 9:57 ` [PATCH 1/2] doc: filesystems: proc: Remove stray '-' preventing table output Mike Rapoport
2020-07-14 13:51 ` Jonathan Corbet
2020-07-15 20:44 ` Chris Packham
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=20200714090644.13011-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=adobriyan@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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).