[PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors

[PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors

[Abhash Jha]

In this commit we correct some simple spelling mistakes
in the Documentation/arch directory.

1) "Assitance" to "Assistance"
2) "parant" to "parent"

Signed-off-by: Abhash Jha <abhashkumarjha123@gmail.com>
---
 Documentation/arch/powerpc/ultravisor.rst | 2 +-
 Documentation/arch/riscv/vector.rst       | 2 +-
 Documentation/arch/x86/cpuinfo.rst        | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/arch/powerpc/ultravisor.rst b/Documentation/arch/powerpc/ultravisor.rst
index ba6b1bf1c..6d0407b2f 100644
--- a/Documentation/arch/powerpc/ultravisor.rst
+++ b/Documentation/arch/powerpc/ultravisor.rst
@@ -134,7 +134,7 @@ Hardware
 
       * PTCR and partition table entries (partition table is in secure
         memory). An attempt to write to PTCR will cause a Hypervisor
-        Emulation Assitance interrupt.
+        Emulation Assistance interrupt.
 
       * LDBAR (LD Base Address Register) and IMC (In-Memory Collection)
         non-architected registers. An attempt to write to them will cause a
diff --git a/Documentation/arch/riscv/vector.rst b/Documentation/arch/riscv/vector.rst
index 75dd88a62..e4a28def3 100644
--- a/Documentation/arch/riscv/vector.rst
+++ b/Documentation/arch/riscv/vector.rst
@@ -15,7 +15,7 @@ status for the use of Vector in userspace. The intended usage guideline for
 these interfaces is to give init systems a way to modify the availability of V
 for processes running under its domain. Calling these interfaces is not
 recommended in libraries routines because libraries should not override policies
-configured from the parant process. Also, users must noted that these interfaces
+configured from the parent process. Also, users must noted that these interfaces
 are not portable to non-Linux, nor non-RISC-V environments, so it is discourage
 to use in a portable code. To get the availability of V in an ELF program,
 please read :c:macro:`COMPAT_HWCAP_ISA_V` bit of :c:macro:`ELF_HWCAP` in the
diff --git a/Documentation/arch/x86/cpuinfo.rst b/Documentation/arch/x86/cpuinfo.rst
index 8895784d4..fd7999c4a 100644
--- a/Documentation/arch/x86/cpuinfo.rst
+++ b/Documentation/arch/x86/cpuinfo.rst
@@ -12,7 +12,7 @@ represents an ill-fated attempt from long time ago to put feature flags
 in an easy to find place for userspace.
 
 However, the amount of feature flags is growing by the CPU generation,
-leading to unparseable and unwieldy /proc/cpuinfo.
+leading to unparsable and unwieldy /proc/cpuinfo.
 
 What is more, those feature flags do not even need to be in that file
 because userspace doesn't care about them - glibc et al already use
-- 
2.43.0

[PATCH] LKMP(Bug fixing fall 2024): Fix spelling mistakes in Documentation

[Abhash Jha]

In this patch we fix simple spelling mistakes in singluar words for
the files inside /Documentation/filesystems directory.
1) "ontext" to "context"
2) "poiners" to "pointers"
3) "realtively" to "relatively"
4) "uptream" to "upstream"

Signed-off-by: Abhash Jha <abhashkumarjha123@gmail.com>
---
 Documentation/filesystems/coda.rst                             | 2 +-
 Documentation/filesystems/netfs_library.rst                    | 2 +-
 Documentation/filesystems/xfs/xfs-delayed-logging-design.rst   | 2 +-
 Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/filesystems/coda.rst b/Documentation/filesystems/coda.rst
index bdde7e4e0..0db3c83a5 100644
--- a/Documentation/filesystems/coda.rst
+++ b/Documentation/filesystems/coda.rst
@@ -141,7 +141,7 @@ kernel support.
   a process P which accessing a Coda file. It makes a system call which
   traps to the OS kernel. Examples of such calls trapping to the kernel
   are ``read``, ``write``, ``open``, ``close``, ``create``, ``mkdir``,
-  ``rmdir``, ``chmod`` in a Unix ontext.  Similar calls exist in the Win32
+  ``rmdir``, ``chmod`` in a Unix context.  Similar calls exist in the Win32
   environment, and are named ``CreateFile``.
 
   Generally the operating system handles the request in a virtual
diff --git a/Documentation/filesystems/netfs_library.rst b/Documentation/filesystems/netfs_library.rst
index 4cc657d74..4f0acd1d7 100644
--- a/Documentation/filesystems/netfs_library.rst
+++ b/Documentation/filesystems/netfs_library.rst
@@ -515,7 +515,7 @@ The methods defined in the table are:
    the cache to expand a request in either direction.  This allows the cache to
    size the request appropriately for the cache granularity.
 
-   The function is passed poiners to the start and length in its parameters,
+   The function is passed pointers to the start and length in its parameters,
    plus the size of the file for reference, and adjusts the start and length
    appropriately.  It should return one of:
 
diff --git a/Documentation/filesystems/xfs/xfs-delayed-logging-design.rst b/Documentation/filesystems/xfs/xfs-delayed-logging-design.rst
index 6402ab8e3..2a2705e97 100644
--- a/Documentation/filesystems/xfs/xfs-delayed-logging-design.rst
+++ b/Documentation/filesystems/xfs/xfs-delayed-logging-design.rst
@@ -219,7 +219,7 @@ The log is circular, so the positions in the log are defined by the combination
 of a cycle number - the number of times the log has been overwritten - and the
 offset into the log.  A LSN carries the cycle in the upper 32 bits and the
 offset in the lower 32 bits. The offset is in units of "basic blocks" (512
-bytes). Hence we can do realtively simple LSN based math to keep track of
+bytes). Hence we can do relatively simple LSN based math to keep track of
 available space in the log.
 
 Log space accounting is done via a pair of constructs called "grant heads".  The
diff --git a/Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst b/Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst
index 32b6ac4ca..ce4584fb3 100644
--- a/Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst
+++ b/Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst
@@ -93,7 +93,7 @@ others on a regular basis about burnout.
   sponsoring work on any part of XFS.
 
 - **LTS Maintainer**: Someone who backports and tests bug fixes from
-  uptream to the LTS kernels.
+  upstream to the LTS kernels.
   There tend to be six separate LTS trees at any given time.
 
   The maintainer for a given LTS release should identify themselves with an
-- 
2.43.0

Re: [PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Wed, Aug 14, 2024 at 04:06:18PM +0530, Abhash Jha wrote:

btw, your commit $subject is rather odd, as it contains
"LKMP(Bug fixing fall 2024):".


>  Documentation/arch/riscv/vector.rst       | 2 +-
> --- a/Documentation/arch/riscv/vector.rst
> +++ b/Documentation/arch/riscv/vector.rst
> @@ -15,7 +15,7 @@ status for the use of Vector in userspace. The intended usage guideline for
>  these interfaces is to give init systems a way to modify the availability of V
>  for processes running under its domain. Calling these interfaces is not
>  recommended in libraries routines because libraries should not override policies
> -configured from the parant process. Also, users must noted that these interfaces
> +configured from the parent process. Also, users must noted that these interfaces
                                                        ^^^^^
						There's a second mistake
						in this line.


Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors

[Abhash jha]

> btw, your commit $subject is rather odd, as it contains
> "LKMP(Bug fixing fall 2024):".
I changed it to something appropriate for the mailing list.

> > -configured from the parant process. Also, users must noted that these interfaces
> > +configured from the parent process. Also, users must noted that these interfaces
>                                                         ^^^^^
>                                                 There's a second mistake
>                                                 in this line.
Thanks for pointing it out, I made the changes in v2.
Link : https://lore.kernel.org/linux-doc/20240814113003.14508-1-abhashkumarjha123@gmail.com/T/#u

Regards,
Abhash