From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux F2FS <linux-f2fs-devel@lists.sourceforge.net>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Daeho Jeong <daehojeong@google.com>,
Yuanye Ma <yuanye.ma20@gmail.com>, Yangtao Li <frank.li@vivo.com>
Subject: [PATCH 1/6] Documentation: f2fs: Separate errors mode subtable
Date: Wed, 20 Aug 2025 11:34:27 +0700 [thread overview]
Message-ID: <20250820043432.22509-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250820043432.22509-1-bagasdotme@gmail.com>
errors=%s subtable is shown in htmldocs output as long-running paragraph
instead due to missing separator from its previous paragraph. Add it.
Fixes: b62e71be2110 ("f2fs: support errors=remount-ro|continue|panic mountoption")
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/f2fs.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
index e5bb89452aff29..203631566a2c58 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst
@@ -357,6 +357,7 @@ errors=%s Specify f2fs behavior on critical errors. This supports modes:
panic immediately, continue without doing anything, and remount
the partition in read-only mode. By default it uses "continue"
mode.
+
====================== =============== =============== ========
mode continue remount-ro panic
====================== =============== =============== ========
--
An old man doll... just what I always wanted! - Clara
WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux F2FS <linux-f2fs-devel@lists.sourceforge.net>
Cc: Daeho Jeong <daehojeong@google.com>,
Jonathan Corbet <corbet@lwn.net>, Yangtao Li <frank.li@vivo.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Yuanye Ma <yuanye.ma20@gmail.com>
Subject: [f2fs-dev] [PATCH 1/6] Documentation: f2fs: Separate errors mode subtable
Date: Wed, 20 Aug 2025 11:34:27 +0700 [thread overview]
Message-ID: <20250820043432.22509-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250820043432.22509-1-bagasdotme@gmail.com>
errors=%s subtable is shown in htmldocs output as long-running paragraph
instead due to missing separator from its previous paragraph. Add it.
Fixes: b62e71be2110 ("f2fs: support errors=remount-ro|continue|panic mountoption")
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/f2fs.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
index e5bb89452aff29..203631566a2c58 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst
@@ -357,6 +357,7 @@ errors=%s Specify f2fs behavior on critical errors. This supports modes:
panic immediately, continue without doing anything, and remount
the partition in read-only mode. By default it uses "continue"
mode.
+
====================== =============== =============== ========
mode continue remount-ro panic
====================== =============== =============== ========
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-08-20 4:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 4:34 [PATCH 0/6] f2fs: documentation formatting cleanup and improvements Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20 4:34 ` Bagas Sanjaya [this message]
2025-08-20 4:34 ` [f2fs-dev] [PATCH 1/6] Documentation: f2fs: Separate errors mode subtable Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 2/6] Documentation: f2fs: Format compression level subtable Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 3/6] Documentation: f2fs: Span write hint table section rows Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 4/6] Documentation: f2fs: Wrap snippets in literal code blocks Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 5/6] Documentation: f2fs: Indent compression_mode option list Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 6/6] Documentation: f2fs: Reword title Bagas Sanjaya
2025-08-20 4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-25 1:59 ` [PATCH 0/6] f2fs: documentation formatting cleanup and improvements Chao Yu
2025-08-25 1:59 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-08-29 22:31 ` Jonathan Corbet
2025-08-29 22:31 ` [f2fs-dev] " Jonathan Corbet
2025-08-30 23:56 ` Jaegeuk Kim
2025-08-30 23:56 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-08-31 20:12 ` Jonathan Corbet
2025-08-31 20:12 ` [f2fs-dev] " Jonathan Corbet
2025-09-02 20:20 ` patchwork-bot+f2fs
2025-09-02 20:20 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=20250820043432.22509-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=daehojeong@google.com \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuanye.ma20@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.