From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 01/10] fanotify_init.2: tfix
Date: Sat, 20 Aug 2022 01:28:04 +0200 [thread overview]
Message-ID: <a5484dc8-33a7-e10b-2b73-7a44698a529c@gmail.com> (raw)
In-Reply-To: <20220819190859.6248-1-jwilk@jwilk.net>
[-- Attachment #1.1: Type: text/plain, Size: 1548 bytes --]
Hi Jakub,
On 8/19/22 21:08, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
> ---
> man2/fanotify_init.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/fanotify_init.2 b/man2/fanotify_init.2
> index 9eac6d2d7..262c505fa 100644
> --- a/man2/fanotify_init.2
> +++ b/man2/fanotify_init.2
> @@ -186,7 +186,7 @@ objects by file handles.
> Note that without the flag
> .BR FAN_REPORT_TARGET_FID ,
> for the directory entry modification events,
> -there is an inforamtion record that identifies the modified directory
> +there is an information record that identifies the modified directory
> and not the created/deleted/moved child object.
> The use of
> .B FAN_CLASS_CONTENT
> @@ -477,7 +477,7 @@ users may call
> .BR fanotify_init ()
> without the
> .B CAP_SYS_ADMIN
> -capability to create and intialize an fanotify group with limited functionality.
> +capability to create and initialize an fanotify group with limited functionality.
should this be 'a fanotify' instead of 'an fanotify'?
BTW, I noticed you find a lot of typos. I'm curious: do you find them
when reading, or you run a tool that finds them? If it's the latter,
maybe you'd be interested in adding it to the Makefile, adding a lint-*
target that we can run from time to time?
Cheers,
Alex
> .TP
> The limitations imposed on an event listener created by a user without the
> .B CAP_SYS_ADMIN
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-19 23:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 19:08 [PATCH 01/10] fanotify_init.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 02/10] landlock_restrict_self.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 03/10] memfd_secret.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 04/10] clockid_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 05/10] dev_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 06/10] itimerspec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 07/10] timespec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 08/10] tm.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 09/10] fanotify.7: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 10/10] tcp.7: tfix Jakub Wilk
2022-08-19 23:28 ` Alejandro Colomar [this message]
2022-08-21 5:28 ` [PATCH 01/10] fanotify_init.2: tfix G. Branden Robinson
2022-08-21 11:28 ` Alejandro Colomar
2022-08-22 18:21 ` Jakub Wilk
2022-08-22 19:02 ` Alejandro Colomar
2022-08-19 23:32 ` Alejandro Colomar
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=a5484dc8-33a7-e10b-2b73-7a44698a529c@gmail.com \
--to=alx.manpages@gmail.com \
--cc=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