linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Documentation/filesystems/xfs: Fix typo error
@ 2025-08-21 13:13 Alperen Aksu
  2025-08-21 16:54 ` Randy Dunlap
  2025-08-29 22:26 ` Jonathan Corbet
  0 siblings, 2 replies; 3+ messages in thread
From: Alperen Aksu @ 2025-08-21 13:13 UTC (permalink / raw)
  To: corbet; +Cc: linux-xfs, linux-doc, skhan, linux-kernel-mentees, Alperen Aksu

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

Signed-off-by: Alperen Aksu <aksulperen@gmail.com>
---
 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


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] Documentation/filesystems/xfs: Fix typo error
  2025-08-21 13:13 [PATCH] Documentation/filesystems/xfs: Fix typo error Alperen Aksu
@ 2025-08-21 16:54 ` Randy Dunlap
  2025-08-29 22:26 ` Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2025-08-21 16:54 UTC (permalink / raw)
  To: Alperen Aksu, corbet; +Cc: linux-xfs, linux-doc, skhan, linux-kernel-mentees



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 <aksulperen@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  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.

>  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] Documentation/filesystems/xfs: Fix typo error
  2025-08-21 13:13 [PATCH] Documentation/filesystems/xfs: Fix typo error Alperen Aksu
  2025-08-21 16:54 ` Randy Dunlap
@ 2025-08-29 22:26 ` Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2025-08-29 22:26 UTC (permalink / raw)
  To: Alperen Aksu
  Cc: linux-xfs, linux-doc, skhan, linux-kernel-mentees, Alperen Aksu

Alperen Aksu <aksulperen@gmail.com> writes:

> Fixed typo error in referring to the section's headline
> Fixed to correct spelling of "mapping"
>
> Signed-off-by: Alperen Aksu <aksulperen@gmail.com>
> ---
>  Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied, thanks.

jon

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-08-29 22:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-21 13:13 [PATCH] Documentation/filesystems/xfs: Fix typo error Alperen Aksu
2025-08-21 16:54 ` Randy Dunlap
2025-08-29 22:26 ` Jonathan Corbet

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).