Documentation/filesystems/xfs: Fix typo error

Started by Alperen Aksu on Aug 21, 2025 · 3 messages from 3 authors · Last reply Aug 29, 2025

Subsystems (3)

Maintainers (3)

STALE427d LANDED

Status: Landed in mainline as ba653158f40d on 2025-08-29.

open the first message on its own page

  1. [PATCH] Documentation/filesystems/xfs: Fix typo error
    Related patches

[PATCH] Documentation/filesystems/xfs: Fix typo error

From: Alperen Aksu <hidden>
Date: 2025-08-21 13:17:23

Fixed typo error in referring to the section's headline
Fixed to correct spelling of "mapping"

Signed-off-by: Alperen Aksu <redacted>
---
 Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
index e231d127cd40..b39b588bb995 100644
--- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
+++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
@@ -475,7 +475,7 @@ operation, which may cause application failure or an unplanned filesystem
 shutdown.
 
 Inspiration for the secondary metadata repair strategy was drawn from section
-2.4 of Srinivasan above, and sections 2 ("NSF: Inded Build Without Side-File")
+2.4 of Srinivasan above, and sections 2 ("NSF: Index Build Without Side-File")
 and 3.1.1 ("Duplicate Key Insert Problem") in C. Mohan, `"Algorithms for
 Creating Indexes for Very Large Tables Without Quiescing Updates"
 <https://dl.acm.org/doi/10.1145/130283.130337>`_, 1992.
@@ -4179,7 +4179,7 @@ When the exchange is initiated, the sequence of operations is as follows:
    This will be discussed in more detail in subsequent sections.
 
 If the filesystem goes down in the middle of an operation, log recovery will
-find the most recent unfinished maping exchange log intent item and restart
+find the most recent unfinished mapping exchange log intent item and restart
 from there.
 This is how atomic file mapping exchanges guarantees that an outside observer
 will either see the old broken structure or the new one, and never a mismash of
-- 
2.43.0

Re: [PATCH] Documentation/filesystems/xfs: Fix typo error

From: Randy Dunlap <rdunlap@infradead.org>
Date: 2025-08-21 16:54:23


On 8/21/25 6:13 AM, Alperen Aksu wrote:
Fixed typo error in referring to the section's headline
Fixed to correct spelling of "mapping"

Signed-off-by: Alperen Aksu <redacted>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
quoted hunk
---
 Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
index e231d127cd40..b39b588bb995 100644
--- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
+++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
@@ -475,7 +475,7 @@ operation, which may cause application failure or an unplanned filesystem
 shutdown.
 
 Inspiration for the secondary metadata repair strategy was drawn from section
-2.4 of Srinivasan above, and sections 2 ("NSF: Inded Build Without Side-File")
+2.4 of Srinivasan above, and sections 2 ("NSF: Index Build Without Side-File")
 and 3.1.1 ("Duplicate Key Insert Problem") in C. Mohan, `"Algorithms for
In the PDF that I looked at, section 3.1.1 is

  3.1.1. Duplicate-Key-Insert Problem

if it matters.
quoted hunk
 Creating Indexes for Very Large Tables Without Quiescing Updates"
 <https://dl.acm.org/doi/10.1145/130283.130337>`_, 1992.
@@ -4179,7 +4179,7 @@ When the exchange is initiated, the sequence of operations is as follows:
    This will be discussed in more detail in subsequent sections.
 
 If the filesystem goes down in the middle of an operation, log recovery will
-find the most recent unfinished maping exchange log intent item and restart
+find the most recent unfinished mapping exchange log intent item and restart
 from there.
 This is how atomic file mapping exchanges guarantees that an outside observer
 will either see the old broken structure or the new one, and never a mismash of

thanks.
-- 
~Randy

Re: [PATCH] Documentation/filesystems/xfs: Fix typo error

From: Jonathan Corbet <corbet@lwn.net>
Date: 2025-08-29 22:26:58

Alperen Aksu [off-list ref] writes:
Fixed typo error in referring to the section's headline
Fixed to correct spelling of "mapping"

Signed-off-by: Alperen Aksu <redacted>
---
 Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.

jon
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help