From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 3/3] fanotify.7, fanotify_mark.2: Clarify FAN_ONDIR in output mask
Date: Sun, 7 Jun 2020 22:40:09 +1000 [thread overview]
Message-ID: <20200607124009.GC4886@mail.bobrowski.net> (raw)
In-Reply-To: <20200529092530.25207-4-amir73il@gmail.com>
On Fri, May 29, 2020 at 12:25:30PM +0300, Amir Goldstein wrote:
> FAN_ONDIR has been an input only flag before introduing FAN_REPORT_FID.
> With FAN_REPORT_FID it can also be in output mask.
>
> Move the text describing its role in output mask to fanotify.7 where the
> other output mask bits are documented.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
This also looks good to me!
Reviewed-by: Matthew Bobrowski <mbobrowski@mbobrowski.org>
/M
next prev parent reply other threads:[~2020-06-07 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 9:25 [PATCH 0/3] fanotify man page updates for final v5.7 Amir Goldstein
2020-05-29 9:25 ` [PATCH 1/3] Revert "fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY" Amir Goldstein
2020-06-07 12:15 ` Matthew Bobrowski
2020-06-08 20:13 ` Michael Kerrisk (man-pages)
2020-05-29 9:25 ` [PATCH 2/3] fanotify_init.2: move out of place entry FAN_REPORT_FID Amir Goldstein
2020-06-07 12:24 ` Matthew Bobrowski
2020-06-08 20:15 ` Michael Kerrisk (man-pages)
2020-05-29 9:25 ` [PATCH 3/3] fanotify.7, fanotify_mark.2: Clarify FAN_ONDIR in output mask Amir Goldstein
2020-06-07 12:40 ` Matthew Bobrowski [this message]
2020-06-08 20:18 ` Michael Kerrisk (man-pages)
2020-06-03 10:26 ` [PATCH 0/3] fanotify man page updates for final v5.7 Michael Kerrisk (man-pages)
2020-06-03 23:57 ` Matthew Bobrowski
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=20200607124009.GC4886@mail.bobrowski.net \
--to=mbobrowski@mbobrowski.org \
--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;
as well as URLs for NNTP newsgroup(s).