Documentation: Fix documentation typos
Subsystems (3)
PATCH 1/1 Documentation: Fix documentation typos
Fix several spelling mistakes in documentation:
- Availablity -> Availability
- heirarchy -> hierarchy
- maping -> mapping
Findings are based on v6.17-rc2.
--- Documentation/admin-guide/cgroup-v2.rst | 2 +- Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++--- Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-)
Documentation/admin-guide/cgroup-v2.rst +1 -1
@@ -435,7 +435,7 @@ both cgroups. Controlling Controllers ----------------------- -Availablity +Availability ~~~~~~~~~~~ A controller is available in a cgroup when it is supported by the kernel (i.e.,
Documentation/filesystems/bcachefs/future/idle_work.rst +3 -3
@@ -11,10 +11,10 @@ idle" so the system can go to sleep. We don't want to be dribbling out background work while the system should be idle. The complicating factor is that there are a number of background tasks, which -form a heirarchy (or a digraph, depending on how you divide it up) - one +form a hierarchy (or a digraph, depending on how you divide it up) - one background task may generate work for another. -Thus proper idle detection needs to model this heirarchy. +Thus proper idle detection needs to model this hierarchy. - Foreground writes - Page cache writeback
@@ -51,7 +51,7 @@ IDLE REGIME When the system becomes idle, we should start flushing our pending work quicker so the system can go to sleep. -Note that the definition of "idle" depends on where in the heirarchy a task +Note that the definition of "idle" depends on where in the hierarchy a task is - a task should start flushing work more quickly when the task above it has stopped generating new work.
Documentation/filesystems/xfs/xfs-online-fsck-design.rst +1 -1
@@ -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
Signature · 1 line
2.34.1
Quoted 7 lines · Sahil Chandna
Fix several spelling mistakes in documentation:
- Availablity -> Availability
- heirarchy -> hierarchy
- maping -> mapping
Findings are based on v6.17-rc2.
Quoted 7 lines
Signed-off-by Sahil Chandna <[email protected]>--- Documentation/admin-guide/cgroup-v2.rst | 2 +- Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++--- Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-)
Looks good, although there was just another patch that also fixed the maping/mapping spelling for XFS.
And various maintainers might request that you split the patch up by subsystem/filesystem (i.e., 3 patches here) unless Jon merges it as is.
thanks.
Signature · 1 line
~Randy
Quoted 18 lines · Randy Dunlap
Quoted 7 lines · Sahil Chandna
Fix several spelling mistakes in documentation:
- Availablity -> Availability
- heirarchy -> hierarchy
- maping -> mapping
Findings are based on v6.17-rc2.Quoted 7 lines
Signed-off-by Sahil Chandna <[email protected]>--- Documentation/admin-guide/cgroup-v2.rst | 2 +- Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++--- Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-)
Quoted 7 lines
Looks good, although there was just another patch that also fixed the maping/mapping spelling for XFS.
And various maintainers might request that you split the patch up by subsystem/filesystem (i.e., 3 patches here) unless Jon merges it as is.
Reviewed-by Randy Dunlap <[email protected]>
I'll take the bcachefs patch if it's split up.