public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack3000@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Quentin Monnet <quentin@isovalent.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH] mount_setattr.2, openat2.2, landlock.7: wfix
Date: Sat, 22 Apr 2023 22:17:55 +0200	[thread overview]
Message-ID: <20230422.a974761497ef@gnoack.org> (raw)
In-Reply-To: <20230422150646.5263-1-gnoack3000@gmail.com>

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
> 

  reply	other threads:[~2023-04-22 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 15:06 [PATCH] mount_setattr.2, openat2.2, landlock.7: wfix Günther Noack
2023-04-22 20:17 ` Günther Noack [this message]
2023-04-23 16:03 ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230422.a974761497ef@gnoack.org \
    --to=gnoack3000@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=quentin@isovalent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox