[PATCH] mount_setattr.2, openat2.2, landlock.7: wfix

[PATCH] mount_setattr.2, openat2.2, landlock.7: wfix

[Günther Noack]

Fix spelling of "run time", as documented in man-pages(7):

* "run time" in two words when used as a noun
* "run-time" with hyphen when used as an adjective

There is another occurrence in bpf-helpers.7,
but that content gets generated from the kernel source
and should be fixed there.

Signed-off-by: Günther Noack <gnoack3000@gmail.com>
---
 man2/mount_setattr.2 | 2 +-
 man2/openat2.2       | 2 +-
 man7/landlock.7      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index 24801a4bd..8df02641a 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -862,7 +862,7 @@ may change in the future
 user-space applications should zero-fill
 .I struct mount_attr
 to ensure that recompiling the program with new headers will not result in
-spurious errors at runtime.
+spurious errors at run time.
 The simplest way is to use a designated initializer:
 .PP
 .in +4n
diff --git a/man2/openat2.2 b/man2/openat2.2
index e90211fad..182851089 100644
--- a/man2/openat2.2
+++ b/man2/openat2.2
@@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are
 updated), user-space applications should zero-fill
 .I struct open_how
 to ensure that recompiling the program with new headers will not result in
-spurious errors at runtime.
+spurious errors at run time.
 The simplest way is to use a designated
 initializer:
 .PP
diff --git a/man7/landlock.7 b/man7/landlock.7
index b6c9d3821..df7b87e80 100644
--- a/man7/landlock.7
+++ b/man7/landlock.7
@@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants.
 This allows creating standalone and modular security policies
 per application,
 which will automatically be composed between themselves
-according to their runtime parent policies.
+according to their run-time parent policies.
 .\"
 .SS Ptrace restrictions
 A sandboxed process has less privileges than a non-sandboxed process and

base-commit: 59e44e4511391a98f531c08aaba17391f3b7075b
-- 
2.40.0

Re: [PATCH] mount_setattr.2, openat2.2, landlock.7: wfix

[Günther Noack]

Whoops, this was meant to be a "V2" patch, of course...

–Günther

On Sat, Apr 22, 2023 at 05:06:46PM +0200, Günther Noack wrote:
> Fix spelling of "run time", as documented in man-pages(7):
> 
> * "run time" in two words when used as a noun
> * "run-time" with hyphen when used as an adjective
> 
> There is another occurrence in bpf-helpers.7,
> but that content gets generated from the kernel source
> and should be fixed there.
> 
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
> ---
>  man2/mount_setattr.2 | 2 +-
>  man2/openat2.2       | 2 +-
>  man7/landlock.7      | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
> index 24801a4bd..8df02641a 100644
> --- a/man2/mount_setattr.2
> +++ b/man2/mount_setattr.2
> @@ -862,7 +862,7 @@ may change in the future
>  user-space applications should zero-fill
>  .I struct mount_attr
>  to ensure that recompiling the program with new headers will not result in
> -spurious errors at runtime.
> +spurious errors at run time.
>  The simplest way is to use a designated initializer:
>  .PP
>  .in +4n
> diff --git a/man2/openat2.2 b/man2/openat2.2
> index e90211fad..182851089 100644
> --- a/man2/openat2.2
> +++ b/man2/openat2.2
> @@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are
>  updated), user-space applications should zero-fill
>  .I struct open_how
>  to ensure that recompiling the program with new headers will not result in
> -spurious errors at runtime.
> +spurious errors at run time.
>  The simplest way is to use a designated
>  initializer:
>  .PP
> diff --git a/man7/landlock.7 b/man7/landlock.7
> index b6c9d3821..df7b87e80 100644
> --- a/man7/landlock.7
> +++ b/man7/landlock.7
> @@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants.
>  This allows creating standalone and modular security policies
>  per application,
>  which will automatically be composed between themselves
> -according to their runtime parent policies.
> +according to their run-time parent policies.
>  .\"
>  .SS Ptrace restrictions
>  A sandboxed process has less privileges than a non-sandboxed process and
> 
> base-commit: 59e44e4511391a98f531c08aaba17391f3b7075b
> -- 
> 2.40.0
> 

Re: [PATCH] mount_setattr.2, openat2.2, landlock.7: wfix

[Alejandro Colomar]

[-- Attachment #1.1: Type: text/plain, Size: 2884 bytes --]

Hi!

On 4/22/23 17:06, Günther Noack wrote:
> Fix spelling of "run time", as documented in man-pages(7):
> 
> * "run time" in two words when used as a noun
> * "run-time" with hyphen when used as an adjective
> 
> There is another occurrence in bpf-helpers.7,
> but that content gets generated from the kernel source
> and should be fixed there.
> 
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>

Patch applied, with minor tweaks to the commit log:

    man*/: wfix
    
    Fix spelling of "run time", as documented in man-pages(7):
    
    -  "run time" in two words when used as a noun
    -  "run-time" with hyphen when used as an adjective
    
    There is another occurrence in bpf-helpers.7,
    but that content gets generated from the kernel source
    and should be fixed there.
    
    Signed-off-by: Günther Noack <gnoack3000@gmail.com>
    Signed-off-by: Alejandro Colomar <alx@kernel.org>


Cheers!
Alex

> ---
>  man2/mount_setattr.2 | 2 +-
>  man2/openat2.2       | 2 +-
>  man7/landlock.7      | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
> index 24801a4bd..8df02641a 100644
> --- a/man2/mount_setattr.2
> +++ b/man2/mount_setattr.2
> @@ -862,7 +862,7 @@ may change in the future
>  user-space applications should zero-fill
>  .I struct mount_attr
>  to ensure that recompiling the program with new headers will not result in
> -spurious errors at runtime.
> +spurious errors at run time.
>  The simplest way is to use a designated initializer:
>  .PP
>  .in +4n
> diff --git a/man2/openat2.2 b/man2/openat2.2
> index e90211fad..182851089 100644
> --- a/man2/openat2.2
> +++ b/man2/openat2.2
> @@ -545,7 +545,7 @@ may change in the future (with new fields being added when system headers are
>  updated), user-space applications should zero-fill
>  .I struct open_how
>  to ensure that recompiling the program with new headers will not result in
> -spurious errors at runtime.
> +spurious errors at run time.
>  The simplest way is to use a designated
>  initializer:
>  .PP
> diff --git a/man7/landlock.7 b/man7/landlock.7
> index b6c9d3821..df7b87e80 100644
> --- a/man7/landlock.7
> +++ b/man7/landlock.7
> @@ -251,7 +251,7 @@ will stay enforced on all this thread's descendants.
>  This allows creating standalone and modular security policies
>  per application,
>  which will automatically be composed between themselves
> -according to their runtime parent policies.
> +according to their run-time parent policies.
>  .\"
>  .SS Ptrace restrictions
>  A sandboxed process has less privileges than a non-sandboxed process and
> 
> base-commit: 59e44e4511391a98f531c08aaba17391f3b7075b

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]