From: David Howells <dhowells@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: dhowells@redhat.com, viro@zeniv.linux.org.uk,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-man@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [MANPAGE PATCH] Add manpage for fsinfo(2)
Date: Wed, 09 Oct 2019 13:02:20 +0100 [thread overview]
Message-ID: <17943.1570622540@warthog.procyon.org.uk> (raw)
In-Reply-To: <515a67cd-f847-8885-da30-1eab3931f1fb@gmail.com>
Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> There is no fsinfo(2) in the system call in the kernel currently.
> Will that call still be added,
Hopefully, but I'm not sure it'll be ready by the next merge window.
> or was it replaced by fsconfig(2),
They're different things and not interchangeable.
David
prev parent reply other threads:[~2019-10-09 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <153126249579.14533.18370053915999978123.stgit@warthog.procyon.org.uk>
[not found] ` <153126248868.14533.9751473662727327569.stgit@warthog.procyon.org.uk>
2018-07-10 22:52 ` [MANPAGE PATCH] Add manpages for move_mount(2) and open_tree(2) David Howells
2019-10-09 9:51 ` Michael Kerrisk (man-pages)
2018-07-10 22:54 ` [MANPAGE PATCH] Add manpage for fsopen(2), fspick(2) and fsmount(2) David Howells
2019-10-09 9:52 ` Michael Kerrisk (man-pages)
2018-07-10 22:55 ` [MANPAGE PATCH] Add manpage for fsinfo(2) David Howells
2019-10-09 9:52 ` Michael Kerrisk (man-pages)
2019-10-09 12:02 ` David Howells [this message]
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=17943.1570622540@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).