linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 3/4] fanotify_mark.2: Add kernel version numbers for some FAN_* constants
Date: Mon,  2 Sep 2019 08:55:35 +0200	[thread overview]
Message-ID: <20190902065536.4878-3-jwilk@jwilk.net> (raw)
In-Reply-To: <20190902065536.4878-1-jwilk@jwilk.net>

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---
 man2/fanotify_mark.2 | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2
index 7a497f29c..e62b6d2c2 100644
--- a/man2/fanotify_mark.2
+++ b/man2/fanotify_mark.2
@@ -177,28 +177,35 @@ Create an event when a read-only file or directory is closed.
 Create an event when a file or directory is opened.
 .TP
 .BR FAN_OPEN_EXEC " (since Linux 5.0)"
+.\" commit 9b076f1c0f4869b838a1b7aa0edb5664d47ec8aa
 Create an event when a file is opened with the intent to be executed.
 See NOTES for additional details.
 .TP
-.B FAN_ATTRIB
+.BR FAN_ATTRIB " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when the metadata for a file or directory has changed.
 .TP
-.B FAN_CREATE
+.BR FAN_CREATE " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when a file or directory has been created in a marked
 parent directory.
 .TP
-.B FAN_DELETE
+.BR FAN_DELETE " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when a file or directory has been deleted in a marked
 parent directory.
 .TP
-.B FAN_DELETE_SELF
+.BR FAN_DELETE_SELF " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when a marked file or directory itself is deleted.
 .TP
-.B FAN_MOVED_FROM
+.BR FAN_MOVED_FROM " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when a file or directory has been moved from a marked
 parent directory.
 .TP
-.B FAN_MOVED_TO
+.BR FAN_MOVED_TO " (since Linux 5.1)"
+.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
 Create an event when a file or directory has been moved to a marked parent
 directory.
 .TP
@@ -218,6 +225,7 @@ or
 is required.
 .TP
 .BR FAN_OPEN_EXEC_PERM " (since Linux 5.0)"
+.\" commit 66917a3130f218dcef9eeab4fd11a71cd00cd7c9
 Create an event when a permission to open a file for execution is
 requested.
 An fanotify file descriptor created with
-- 
2.23.0


  parent reply	other threads:[~2019-09-02  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  6:55 [PATCH 1/4] fanotify.7: tfix Jakub Wilk
2019-09-02  6:55 ` [PATCH 2/4] fanotify_mark.2: ffix Jakub Wilk
2019-09-05 13:46   ` Michael Kerrisk (man-pages)
2019-09-02  6:55 ` Jakub Wilk [this message]
2019-09-05 13:47   ` [PATCH 3/4] fanotify_mark.2: Add kernel version numbers for some FAN_* constants Michael Kerrisk (man-pages)
2019-09-02  6:55 ` [PATCH 4/4] fanotify_mark.2: Document FAN_MOVE_SELF Jakub Wilk
2019-09-05 14:05   ` Michael Kerrisk (man-pages)
2019-09-05 13:45 ` [PATCH 1/4] fanotify.7: tfix 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=20190902065536.4878-3-jwilk@jwilk.net \
    --to=jwilk@jwilk.net \
    --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).