From: "Jürg Billeter" <j@bitron.ch>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jürg Billeter" <j@bitron.ch>
Subject: [PATCH] readv.2, io_submit.2: Document RWF_APPEND added in Linux 4.16
Date: Wed, 28 Mar 2018 21:49:11 +0200 [thread overview]
Message-ID: <20180328194911.49632-1-j@bitron.ch> (raw)
Signed-off-by: Jürg Billeter <j@bitron.ch>
---
man2/io_submit.2 | 10 ++++++++++
man2/readv.2 | 10 ++++++++++
2 files changed, 20 insertions(+)
diff --git a/man2/io_submit.2 b/man2/io_submit.2
index 397fd0b75..79fcdfee4 100644
--- a/man2/io_submit.2
+++ b/man2/io_submit.2
@@ -111,6 +111,16 @@ field of the
.I io_event
structure (see
.BR io_getevents (2)).
+.TP
+.BR RWF_APPEND " (since Linux 4.16)"
+.\" commit e1fc742e14e01d84d9693c4aca4ab23da65811fb
+Append data to the end of the file.
+See the description of the flag of the same name in
+.BR pwritev2 (2)
+as well as the description of
+.B O_APPEND
+in
+.BR open (2).
.RE
.TP
.I aio_lio_opcode
diff --git a/man2/readv.2 b/man2/readv.2
index b3b7b9658..668fba576 100644
--- a/man2/readv.2
+++ b/man2/readv.2
@@ -248,6 +248,16 @@ to
.BR EAGAIN .
Currently, this flag is meaningful only for
.BR preadv2 ().
+.TP
+.BR RWF_APPEND " (since Linux 4.16)"
+.\" commit e1fc742e14e01d84d9693c4aca4ab23da65811fb
+Provide a per-write equivalent of the
+.B O_APPEND
+.BR open (2)
+flag.
+This flag is meaningful only for
+.BR pwritev2 (),
+and its effect applies only to the data range written by the system call.
.SH RETURN VALUE
On success,
.BR readv (),
--
2.16.2
next reply other threads:[~2018-03-28 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 19:49 Jürg Billeter [this message]
2018-04-05 17:49 ` [PATCH] readv.2, io_submit.2: Document RWF_APPEND added in Linux 4.16 Michael Kerrisk (man-pages)
2018-04-06 13:51 ` [PATCH v2] " Jürg Billeter
2018-04-12 9:11 ` 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=20180328194911.49632-1-j@bitron.ch \
--to=j@bitron.ch \
--cc=linux-kernel@vger.kernel.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