From: Jakub Wilk <jwilk@jwilk.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>
Subject: [PATCH 09/10] fanotify.7: tfix
Date: Fri, 19 Aug 2022 21:08:58 +0200 [thread overview]
Message-ID: <20220819190859.6248-9-jwilk@jwilk.net> (raw)
In-Reply-To: <20220819190859.6248-1-jwilk@jwilk.net>
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---
man7/fanotify.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man7/fanotify.7 b/man7/fanotify.7
index 7edfea9a8..d6b816a5b 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -184,7 +184,7 @@ structure.
Importantly,
fanotify provides no guarantee around
the ordering of information records
-when a notification group is intialized with a
+when a notification group is initialized with a
stacked based configuration.
Each information record has a nested structure of type
.IR fanotify_event_info_header .
--
2.37.2
next prev parent reply other threads:[~2022-08-19 19:17 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 ` Jakub Wilk [this message]
2022-08-19 19:08 ` [PATCH 10/10] tcp.7: tfix Jakub Wilk
2022-08-19 23:28 ` [PATCH 01/10] fanotify_init.2: tfix Alejandro Colomar
2022-08-21 5:28 ` 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=20220819190859.6248-9-jwilk@jwilk.net \
--to=jwilk@jwilk.net \
--cc=alx.manpages@gmail.com \
--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