From: David Howells <dhowells@redhat.com>
To: Walter Harms <wharms@bfs.de>
Cc: dhowells@redhat.com,
"mtk.manpages@gmail.com" <mtk.manpages@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"christian.brauner@ubuntu.com" <christian.brauner@ubuntu.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AW: [PATCH 5/5] Add manpage for fsconfig(2)
Date: Fri, 07 Aug 2020 17:27:34 +0100 [thread overview]
Message-ID: <45107.1596817654@warthog.procyon.org.uk> (raw)
In-Reply-To: <a2fe568438aa45e9a63a3a7d9d64a73f@bfs.de>
Walter Harms <wharms@bfs.de> wrote:
> maybe it is obvious but i did not see it ..
> starting with what kernel version are these features available ?
See:
+.SH VERSIONS
+.BR fsconfig ()
+was added to Linux in kernel 5.1.
David
next prev parent reply other threads:[~2020-08-07 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:02 [PATCH 1/5] Add manpage for open_tree(2) David Howells
2020-08-07 14:02 ` [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2) David Howells
2020-08-22 20:04 ` Michael Kerrisk (man-pages)
2020-08-24 10:08 ` David Howells
2020-08-26 7:31 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 3/5] Add manpage for fspick(2) David Howells
2020-08-22 20:05 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2) David Howells
2020-08-22 20:08 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 5/5] Add manpage for fsconfig(2) David Howells
2020-08-07 15:58 ` AW: " Walter Harms
2020-08-07 16:27 ` David Howells [this message]
2020-08-07 16:35 ` AW: " Walter Harms
2020-08-22 20:18 ` Michael Kerrisk (man-pages)
2020-08-22 20:01 ` [PATCH 1/5] Add manpage for open_tree(2) Michael Kerrisk (man-pages)
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=45107.1596817654@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=christian.brauner@ubuntu.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=wharms@bfs.de \
/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).