From: Amir Goldstein <amir73il@gmail.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-man@vger.kernel.org
Subject: [PATCH 0/4] fanotify updates for v5.7
Date: Mon, 20 Apr 2020 21:42:55 +0300 [thread overview]
Message-ID: <20200420184259.29406-1-amir73il@gmail.com> (raw)
Hi Michael,
Following patches include fixes to earlier FAN_REPORT_FID change from
v5.1 and an update for the new event FAN_DIR_MODIFY that has a new
event format.
Those patches were reviewed by Jan and Matthew earlier on github.
Thanks,
Amir.
Amir Goldstein (4):
fanotify_mark.2: Clarification about FAN_MARK_MOUNT and FAN_REPORT_FID
fanotify_mark.2: Clarification about FAN_EVENT_ON_CHILD and new events
fanotify.7: Fix fanotify_fid.c example
fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY
man2/fanotify_mark.2 | 89 ++++++++++++++++++++++++++++++++---
man7/fanotify.7 | 107 +++++++++++++++++++++++++++++++++----------
2 files changed, 165 insertions(+), 31 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-20 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 18:42 Amir Goldstein [this message]
2020-04-20 18:42 ` [PATCH 1/4] fanotify_mark.2: Clarification about FAN_MARK_MOUNT and FAN_REPORT_FID Amir Goldstein
2020-04-20 19:00 ` Michael Kerrisk (man-pages)
2020-04-20 18:42 ` [PATCH 2/4] fanotify_mark.2: Clarification about FAN_EVENT_ON_CHILD and new events Amir Goldstein
2020-04-20 19:03 ` Michael Kerrisk (man-pages)
2020-04-20 18:42 ` [PATCH 3/4] fanotify.7: Fix fanotify_fid.c example Amir Goldstein
2020-04-20 19:06 ` Michael Kerrisk (man-pages)
2020-04-20 18:42 ` [PATCH 4/4] fanotify.7, fanotify_mark.2: Document FAN_DIR_MODIFY Amir Goldstein
2020-04-20 19:25 ` Michael Kerrisk (man-pages)
2020-04-20 19:36 ` [PATCH 0/4] fanotify updates for v5.7 Michael Kerrisk (man-pages)
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=20200420184259.29406-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mbobrowski@mbobrowski.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).