linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: linux-man@vger.kernel.org
Cc: Petr Vorel <pvorel@suse.cz>, David Howells <dhowells@redhat.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Zorro Lang <zlang@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] New mount API syscalls
Date: Fri,  7 Feb 2020 18:42:34 +0100	[thread overview]
Message-ID: <20200207174236.18882-1-pvorel@suse.cz> (raw)

Hi David, Michael,

looks like David's patches to add new mount API syscalls, so I dared to
resent them. I've just changed kernel version to 5.2, fixed typos in
flags and added my tags. + added some questions in patches themselves.

Feel free to send final version in v3.

Kind regards,
Petr

David Howells (2):
  Add manpages for move_mount(2) and open_tree(2)
  Add manpage for fsopen(2), fspick(2) and fsmount(2)

 man2/fsconfig.2   | 282 ++++++++++++++++++++++++++++++++++++++++++++++
 man2/fsmount.2    |   1 +
 man2/fsopen.2     | 256 +++++++++++++++++++++++++++++++++++++++++
 man2/fspick.2     | 195 ++++++++++++++++++++++++++++++++
 man2/move_mount.2 | 271 ++++++++++++++++++++++++++++++++++++++++++++
 man2/open_tree.2  | 260 ++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 1265 insertions(+)
 create mode 100644 man2/fsconfig.2
 create mode 100644 man2/fsmount.2
 create mode 100644 man2/fsopen.2
 create mode 100644 man2/fspick.2
 create mode 100644 man2/move_mount.2
 create mode 100644 man2/open_tree.2

-- 
2.24.1


             reply	other threads:[~2020-02-07 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 17:42 Petr Vorel [this message]
2020-02-07 17:42 ` [PATCH v2 1/2] Add manpages for move_mount(2) and open_tree(2) Petr Vorel
2020-02-26 11:48   ` Petr Vorel
2020-02-07 17:42 ` [PATCH v2 2/2] Add manpage for fsopen(2), fspick(2) and fsmount(2) Petr Vorel

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=20200207174236.18882-1-pvorel@suse.cz \
    --to=pvorel@suse.cz \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=zlang@redhat.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).