Re: [PATCH] typos: Fix 'namespace' typos

[Dr. David Alan Gilbert]

* linux@xxxxxxxxxxx (linux@xxxxxxxxxxx) wrote:
> From: "Dr. David Alan Gilbert" <linux@xxxxxxxxxxx>
> 
> 'namespace' is creatively typo'd in a few different places
> 
> Signed-off-by: Dr. David Alan Gilbert <linux@xxxxxxxxxxx>

Ping.
(and added a couple more cc'c)

> ---
> I've added 'namesapce' to codespell: https://github.com/codespell-project/codespell/commit/cfe751aedb234e262d7e32c1d568939c2ccd4e36
> I wasn't sure if it was worth splitting this into 3 patches given the
> different areas; please advise.
> ---
>  Documentation/driver-api/nvdimm/nvdimm.rst | 2 +-
>  Documentation/filesystems/proc.rst         | 2 +-
>  Documentation/networking/sysfs-tagging.rst | 2 +-
>  drivers/infiniband/core/device.c           | 2 +-
>  include/linux/nd.h                         | 2 +-
>  5 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/driver-api/nvdimm/nvdimm.rst b/Documentation/driver-api/nvdimm/nvdimm.rst
> index be8587a558e1e..ca16b5acbf30d 100644
> --- a/Documentation/driver-api/nvdimm/nvdimm.rst
> +++ b/Documentation/driver-api/nvdimm/nvdimm.rst
> @@ -82,7 +82,7 @@ LABEL:
>    Metadata stored on a DIMM device that partitions and identifies
>    (persistently names) capacity allocated to different PMEM namespaces. It
>    also indicates whether an address abstraction like a BTT is applied to
> -  the namepsace.  Note that traditional partition tables, GPT/MBR, are
> +  the namespace.  Note that traditional partition tables, GPT/MBR, are
>    layered on top of a PMEM namespace, or an address abstraction like BTT
>    if present, but partition support is deprecated going forward.
>  
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 1bc91fb8c321a..335d028752d45 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -2187,7 +2187,7 @@ are not related to tasks.
>  Chapter 5: Filesystem behavior
>  ==============================
>  
> -Originally, before the advent of pid namepsace, procfs was a global file
> +Originally, before the advent of pid namespace, procfs was a global file
>  system. It means that there was only one procfs instance in the system.
>  
>  When pid namespace was added, a separate procfs instance was mounted in
> diff --git a/Documentation/networking/sysfs-tagging.rst b/Documentation/networking/sysfs-tagging.rst
> index 83647e10c2078..65307130ab633 100644
> --- a/Documentation/networking/sysfs-tagging.rst
> +++ b/Documentation/networking/sysfs-tagging.rst
> @@ -43,6 +43,6 @@ Users of this interface:
>  
>    - current_ns() which returns current's namespace
>    - netlink_ns() which returns a socket's namespace
> -  - initial_ns() which returns the initial namesapce
> +  - initial_ns() which returns the initial namespace
>  
>  - call kobj_ns_exit() when an individual tag is no longer valid
> diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
> index d275db195f1a1..0af50a1f53418 100644
> --- a/drivers/infiniband/core/device.c
> +++ b/drivers/infiniband/core/device.c
> @@ -132,7 +132,7 @@ MODULE_PARM_DESC(netns_mode,
>   * rdma_dev_access_netns() - Return whether an rdma device can be accessed
>   *			     from a specified net namespace or not.
>   * @dev:	Pointer to rdma device which needs to be checked
> - * @net:	Pointer to net namesapce for which access to be checked
> + * @net:	Pointer to net namespace for which access to be checked
>   *
>   * When the rdma device is in shared mode, it ignores the net namespace.
>   * When the rdma device is exclusive to a net namespace, rdma device net
> diff --git a/include/linux/nd.h b/include/linux/nd.h
> index b9771ba1ef879..7095faf4a0c85 100644
> --- a/include/linux/nd.h
> +++ b/include/linux/nd.h
> @@ -179,7 +179,7 @@ static inline int nvdimm_read_bytes(struct nd_namespace_common *ndns,
>   * @buf: buffer to drain
>   * @size: transfer length
>   *
> - * NVDIMM Namepaces disks do not implement sectors internally.  Depending on
> + * NVDIMM Namespaces disks do not implement sectors internally.  Depending on
>   * the @ndns, the contents of @buf may be in cpu cache, platform buffers,
>   * or on backing memory media upon return from this routine.  Flushing
>   * to media is handled internal to the @ndns driver, if at all.
> -- 
> 2.36.1
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/