linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-api@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, amir73il@gmail.com, jack@suse.cz
Subject: [RFC PATCH 0/1] fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_REPORT_FID and Directory entry events
Date: Tue, 12 Mar 2019 13:48:34 +1100	[thread overview]
Message-ID: <cover.1552336628.git.mbobrowski@mbobrowski.org> (raw)

This patch contains the updates needed to support the new FAN_REPORT_FID flag
and directory entry modification events.

This is a new fanoitfy API feature that has been recently merged into
upstream master so looking to get some early feedback on the documentation
side of things.

Matthew Bobrowski (1):
  fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_REPORT_FID
    and directory modification events

 man2/fanotify_init.2 |  29 ++++
 man2/fanotify_mark.2 |  93 ++++++++++++-
 man7/fanotify.7      | 313 +++++++++++++++++++++++++++++++++++++++++--
 3 files changed, 425 insertions(+), 10 deletions(-)

-- 
2.17.2


-- 
Matthew Bobrowski

             reply	other threads:[~2019-03-12  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12  2:48 Matthew Bobrowski [this message]
2019-03-12  2:48 ` [RFC PATCH 1/1] fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_REPORT_FID and directory modification events Matthew Bobrowski
2019-03-13 15:07   ` Jan Kara
2019-03-13 15:51     ` Amir Goldstein
2019-03-16 12:35     ` Matthew Bobrowski
2019-03-18 10:01       ` Jan Kara
2019-03-18 11:05         ` Amir Goldstein
2019-03-19 12:06           ` 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=cover.1552336628.git.mbobrowski@mbobrowski.org \
    --to=mbobrowski@mbobrowski.org \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).