From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 4/4] fanotify_mark.2: Document FAN_MOVE_SELF
Date: Thu, 5 Sep 2019 16:05:42 +0200 [thread overview]
Message-ID: <009dce08-607b-bddf-dcd1-aa55f5e5415f@gmail.com> (raw)
In-Reply-To: <20190902065536.4878-4-jwilk@jwilk.net>
Hello Jakub,
On 9/2/19 8:55 AM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Patch applied.
Thanks,
Michael
> ---
> man2/fanotify_mark.2 | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/man2/fanotify_mark.2 b/man2/fanotify_mark.2
> index e62b6d2c2..7c21cc22b 100644
> --- a/man2/fanotify_mark.2
> +++ b/man2/fanotify_mark.2
> @@ -209,6 +209,10 @@ parent directory.
> Create an event when a file or directory has been moved to a marked parent
> directory.
> .TP
> +.BR FAN_MOVE_SELF " (since Linux 5.1)"
> +.\" commit 235328d1fa4251c6dcb32351219bb553a58838d2
> +Create an event when a marked file or directory itself has been moved.
> +.TP
> .B FAN_Q_OVERFLOW
> Create an event when an overflow of the event queue occurs.
> The size of the event queue is limited to 16384 entries if
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2019-09-05 14:05 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 ` [PATCH 3/4] fanotify_mark.2: Add kernel version numbers for some FAN_* constants Jakub Wilk
2019-09-05 13:47 ` 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) [this message]
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=009dce08-607b-bddf-dcd1-aa55f5e5415f@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
/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).