typos: Fix 'namespace' typos
Subsystems (5)
PATCH 1/1 typos: Fix 'namespace' typos
From: "Dr. David Alan Gilbert" <[email protected]>
'namespace' is creatively typo'd in a few different places
---
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(-)
Documentation/driver-api/nvdimm/nvdimm.rst +1 -1
@@ -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.
Documentation/filesystems/proc.rst +1 -1
@@ -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
Documentation/networking/sysfs-tagging.rst +1 -1
@@ -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
drivers/infiniband/core/device.c +1 -1
@@ -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
include/linux/nd.h +1 -1
@@ -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.
Signature · 1 line
2.36.1
Quoted 5 lines · * [email protected] ([email protected]) wrote:
From: "Dr. David Alan Gilbert" <[email protected]>
'namespace' is creatively typo'd in a few different places
Signed-off-by Dr. David Alan Gilbert <[email protected]>
Ping.
(and added a couple more cc'c)
Quoted 79 lines
---
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(-)Documentation/driver-api/nvdimm/nvdimm.rst +1
-1@@ -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.Documentation/filesystems/proc.rst +1
-1@@ -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 inDocumentation/networking/sysfs-tagging.rst +1
-1@@ -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 validdrivers/infiniband/core/device.c +1
-1@@ -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 include/linux/nd.h +1
-1@@ -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. Signature · 1 line
2.36.1
Signature · 4 lines
-----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 |_______/