From: Gou Hao <gouhao@uniontech.com>
To: cem@kernel.org, corbet@lwn.net, hch@lst.de, djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, gouhaojake@163.com,
guanwentao@uniontech.com
Subject: [PATCH V2] xfs-doc: Fix typo error
Date: Wed, 5 Nov 2025 09:35:06 +0800 [thread overview]
Message-ID: <20251105013506.358-1-gouhao@uniontech.com> (raw)
In-Reply-To: <20251104093406.9135-1-gouhao@uniontech.com>
Hi Christoph, Darrick,
Thank you for the reviews. Here is the v2 patch with the commit message fixed as suggested.
Subject: [PATCH V2] xfs-doc: Fix typo error
Online fsck may take longer than offline fsck...
Signed-off-by: Gou Hao <gouhao@uniontech.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
---
Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
index 8cbcd3c26434..55e727b5f12e 100644
--- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
+++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
@@ -249,7 +249,7 @@ sharing and lock acquisition rules as the regular filesystem.
This means that scrub cannot take *any* shortcuts to save time, because doing
so could lead to concurrency problems.
In other words, online fsck is not a complete replacement for offline fsck, and
-a complete run of online fsck may take longer than online fsck.
+a complete run of online fsck may take longer than offline fsck.
However, both of these limitations are acceptable tradeoffs to satisfy the
different motivations of online fsck, which are to **minimize system downtime**
and to **increase predictability of operation**.
--
2.20.1
next prev parent reply other threads:[~2025-11-05 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 9:34 [PATCH] xfs-doc: Fix typo error Gou Hao
2025-11-04 10:57 ` Christoph Hellwig
2025-11-04 16:56 ` Darrick J. Wong
2025-11-05 1:35 ` Gou Hao [this message]
2025-11-10 19:50 ` [PATCH V2] " 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=20251105013506.358-1-gouhao@uniontech.com \
--to=gouhao@uniontech.com \
--cc=cem@kernel.org \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=gouhaojake@163.com \
--cc=guanwentao@uniontech.com \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.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 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.