From: Matthew Bobrowski <repnop@google.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, jack@suse.cz, amir73il@gmail.com,
linux-man@vger.kernel.org
Subject: Re: [PATCH v4] fanotify: Document FAN_REPORT_PIDFD Feature
Date: Tue, 24 May 2022 15:40:47 +1000 [thread overview]
Message-ID: <Yoxv32sx3OYo4pLh@google.com> (raw)
In-Reply-To: <60295764-e14c-9570-8ed3-3975c913e72c@gmail.com>
On Sat, May 14, 2022 at 03:12:33PM +0200, Alejandro Colomar wrote:
> Hi Matthew,
>
> On 4/20/22 00:43, Matthew Bobrowski wrote:
> > Update the fanotify API documentation to include details on the new
> > FAN_REPORT_PIDFD feature. This patch also includes a generic section
> > describing the concept of information records which are supported by
> > the fanotify API.
> >
> > Signed-off-by: Matthew Bobrowski <repnop@google.com>
> > Reviewed-by: Jan Kara <jack@suse.cz>
> > Reviewed-by: Amir Goldstein <amir73il@gmail.com>
> > ---
> >
> > Changes in v4:
> >
> > * Applied style and grammatical suggestions by Alejandro Colomar
> > [0]. This includes the use of Oxford-style commas and semantic
> > newlines.
>
> I've further edited the patch a bit (only whitespace) regarding semantic
> newlines. I'll send it as a reply to this patch in a moment.
>
> Apart from that, I couldn't understand a paragraph. See below.
> > +This is a process file descriptor that refers to the process
> > +responsible for generating the event.
> > +The returned process file descriptor is no different from one which
> > +could be obtained manually if
> > +.BR pidfd_open (2)
> > +were to be called on
> > +.IR fanotify_event_metadata.pid .
>
>
> > +In the instance that an error is encountered during pidfd creation for
> > +one of two possible error types represented by a negative integer
> > +value may be returned in this
> > +.I pidfd
> > +field.
>
> I couldn't understand the paragraph above. Could you maybe rephrase it a
> bit? Maybe add some commas?
I had a read through it and if we drop "for" from that sentence and
add a comma after "creation", then I think this sentence reads
perfectly fine. Having said that, is it necessarsy for me to resend
version 6 (with your semantic newline modifications in addition to
this minor rephrase), or are you OK with just amending these changes
when applying the patch?
/M
next prev parent reply other threads:[~2022-05-24 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 22:43 [PATCH v4] fanotify: Document FAN_REPORT_PIDFD Feature Matthew Bobrowski
2022-05-14 13:12 ` Alejandro Colomar
2022-05-24 5:40 ` Matthew Bobrowski [this message]
2022-05-24 6:06 ` Matthew Bobrowski
2022-05-14 13:13 ` [PATCH v5] " 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=Yoxv32sx3OYo4pLh@google.com \
--to=repnop@google.com \
--cc=alx.manpages@gmail.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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