From: Matthew Bobrowski <repnop@google.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, jack@suse.cz, amir73il@gmail.com,
mtk.manpages@gmail.com
Subject: Re: [PATCH v3] fanotify: Document FAN_REPORT_PIDFD Feature
Date: Wed, 27 Apr 2022 07:23:22 +1000 [thread overview]
Message-ID: <YmhiypE19qp8Ere4@google.com> (raw)
In-Reply-To: <59a8d8b5-fc96-812f-c3b1-d1dca66dca3a@gmail.com>
On Mon, Apr 25, 2022 at 10:18:43PM +0200, Alejandro Colomar wrote:
> Hi Matthew,
>
> On 4/14/22 01:40, Matthew Bobrowski wrote:
> > Haha, I created this patch using one of Amir's branches, as he
> > performed a rebase and handled some conflicts. It must've preserved
> > the display name "Amir Goldstein" in the "From:" header...
>
> :)
>
> >
> > On Wed, Apr 13, 2022 at 08:24:21PM +0200, Alejandro Colomar wrote:
> > > Hi Amir!
> > >
> > > On 4/12/22 01:17, Amir Goldstein 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>
> > >
> > > Thanks for the patch. Please see some comments below.
> >
> > Thanks for the review, I'll update and send through a follow up patch
> > shortly. I left a question on your comment about the use of semantic
> > newlines. I wasn't sure whether that comment was a general rule that
> > is to be applied across this entire patch (in which it definitely can,
> > I just wasn't aware of the rule prior to you explicitly pointing it
> > out), or whether there was a specific example you were referring to in
> > the code block directly above your comment.
>
> General rule to be applied across the entire patch, if you do the favour. I
> just mentioned it at a point where it is clear that it could be applied, to
> give some context.
Fair enough.
I've posted through an updated patch here [0] which I believe has
addressed all the feedback from this round of review.
[0] https://lore.kernel.org/linux-man/1af583adb1f368c51f1976db7bf3a27530cdc06f.1650408011.git.repnop@google.com/
/M
prev parent reply other threads:[~2022-04-26 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 23:17 [PATCH v3] fanotify: Document FAN_REPORT_PIDFD Feature Amir Goldstein
2022-04-13 18:24 ` Alejandro Colomar
2022-04-13 23:40 ` Matthew Bobrowski
2022-04-25 20:18 ` Alejandro Colomar
2022-04-26 21:23 ` Matthew Bobrowski [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=YmhiypE19qp8Ere4@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