public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 (Microsoft)" <brauner@kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Aleksa Sarai <cyphar@cyphar.com>
Subject: [PATCH 0/4] mount_setattr.2: updates
Date: Tue,  7 Jun 2022 15:38:16 +0200	[thread overview]
Message-ID: <20220607133820.1721352-1-brauner@kernel.org> (raw)

From: "Christian Brauner (Microsoft)" <brauner@kernel.org>

Hey everyone,

Here's a set of updates for the mount_setattr.2 man page.
I would really appreciate it if groff syntax could be fixed up by
maintainers. I tried my best to remember the guidelines though. :)

Thanks!
Christian

Christian Brauner (4):
  mount_setattr.2: add and explain missing EBUSY error
  mount_setattr.2: update conditions to create ID-mapped mounts
  mount_setattr.2: update list of supported filesystems
  mount_setattr.2: ffix

 man2/mount_setattr.2 | 64 +++++++++++++++++++++++++++++++++++---------
 1 file changed, 52 insertions(+), 12 deletions(-)


base-commit: ae6b221882ce71ba82fcdbe02419a225111502f0
-- 
2.34.1


             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 Christian Brauner [this message]
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 ` [PATCH 4/4] mount_setattr.2: ffix Christian Brauner
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-1-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