From: Christian Brauner <brauner@kernel.org>
To: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Aleksa Sarai <cyphar@cyphar.com>
Subject: [PATCH 4/4] mount_setattr.2: ffix
Date: Tue, 7 Jun 2022 15:38:20 +0200 [thread overview]
Message-ID: <20220607133820.1721352-5-brauner@kernel.org> (raw)
In-Reply-To: <20220607133820.1721352-1-brauner@kernel.org>
Fix a typo in my name.
Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>
---
man2/mount_setattr.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index 13d66db4f..f1b73e370 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -543,7 +543,7 @@ a new peer group ID needs to be allocated for all mounts without a peer group
ID set.
This allocation failed because
the kernel has run out of IDs.
-.\" Christian Bruner: i.e. someone has somehow managed to
+.\" Christian Brauner: i.e. someone has somehow managed to
.\" allocate so many peer groups and managed to keep the kernel running
.\" (???) that the ida has ran out of ids
.\" Note that technically further error codes are possible that are
--
2.34.1
next prev parent reply other threads:[~2022-06-07 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:38 [PATCH 0/4] mount_setattr.2: updates Christian Brauner
2022-06-07 13:38 ` [PATCH 1/4] mount_setattr.2: add and explain missing EBUSY error Christian Brauner
2022-06-07 13:38 ` [PATCH 2/4] mount_setattr.2: update conditions to create ID-mapped mounts Christian Brauner
2022-06-07 13:38 ` [PATCH 3/4] mount_setattr.2: update list of supported filesystems Christian Brauner
2022-06-07 13:38 ` Christian Brauner [this message]
2022-06-08 15:26 ` [PATCH 0/4] mount_setattr.2: updates Alejandro Colomar
2022-06-08 15:28 ` 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=20220607133820.1721352-5-brauner@kernel.org \
--to=brauner@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=cyphar@cyphar.com \
--cc=hch@infradead.org \
--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