From: "Günther Noack" <gnoack3000@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Quentin Monnet <quentin@isovalent.com>
Subject: Re: [PATCH] mount_setattr.2, openat2.2, bpf-helpers.7, landlock.7: wfix
Date: Sat, 22 Apr 2023 16:59:11 +0200 [thread overview]
Message-ID: <20230422.e80f61bcbc21@gnoack.org> (raw)
In-Reply-To: <d45fce19-e7eb-ed15-3223-df02ba926cc1@gmail.com>
On Fri, Apr 21, 2023 at 09:45:15PM +0200, Alejandro Colomar wrote:
> On 4/21/23 17:05, Günther Noack wrote:
> > --- a/man7/bpf-helpers.7
> > +++ b/man7/bpf-helpers.7
> > @@ -3025,7 +3025,7 @@ copied and the last byte is set to NUL.
> > On success, returns the number of bytes that were written,
> > including the terminal NUL. This makes this helper useful in
> > tracing programs for reading strings, and more importantly to
> > -get its length at runtime. See the following snippet:
> > +get its length at run time. See the following snippet:
>
> Good, but bpf-helpers.7 is generated from kernel sources. This
> one will depend on what kernel developers want. I CCed Quentin,
> since he's nice and might be able to tell if BPF guys are
> interested in this kind of wording fixes.
Ah, whoops, that's a good point.
I'll remove that part of the patch then, because the fix would have to
go in the kernel source.
> > --- 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.
>
> In this case, since it works as an adjective, it should be
> "run-time", with a hyphen.
Thanks, good point. Fixed.
–Günther
prev parent reply other threads:[~2023-04-22 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 15:05 [PATCH] mount_setattr.2, openat2.2, bpf-helpers.7, landlock.7: wfix Günther Noack
2023-04-21 19:45 ` Alejandro Colomar
2023-04-21 21:58 ` Quentin Monnet
2023-04-22 14:59 ` Günther Noack [this message]
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.e80f61bcbc21@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