From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, Jan Kara <jack@suse.cz>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] fanotify.7: fix outdated description
Date: Wed, 25 Nov 2020 12:53:03 +0100 [thread overview]
Message-ID: <20201125115303.GD16944@quack2.suse.cz> (raw)
In-Reply-To: <20201124152109.30027-1-amir73il@gmail.com>
On Tue 24-11-20 17:21:09, Amir Goldstein wrote:
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Looks good to me. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> man7/fanotify.7 | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index c4f5397e4..5804a1f30 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -29,11 +29,12 @@ fanotify \- monitoring filesystem events
> The fanotify API provides notification and interception of
> filesystem events.
> Use cases include virus scanning and hierarchical storage management.
> -Currently, only a limited set of events is supported.
> -In particular, there is no support for create, delete, and move events.
> +In the original fanotify API, only a limited set of events was supported.
> +In particular, there was no support for create, delete, and move events.
> +The support for those events was added in Linux 5.1.
> (See
> .BR inotify (7)
> -for details of an API that does notify those events.)
> +for details of an API that did notify those events pre Linux 5.1.)
> .PP
> Additional capabilities compared to the
> .BR inotify (7)
> --
> 2.17.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-11-25 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 15:21 [PATCH] fanotify.7: fix outdated description Amir Goldstein
2020-11-25 11:53 ` Jan Kara [this message]
2020-11-26 9:48 ` Michael Kerrisk (man-pages)
2020-11-26 13:29 ` Jan Kara
2020-12-30 14:17 ` Michael Kerrisk (man-pages)
2021-01-04 11:55 ` Jan Kara
2021-01-04 13:29 ` 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=20201125115303.GD16944@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--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).