From: Dylan Yudaken <[email protected]>
To: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Cc: <[email protected]>, <[email protected]>,
Dylan Yudaken <[email protected]>
Subject: [PATCH liburing 2/2] update documentation to reflect no 5.20 kernel
Date: Mon, 26 Sep 2022 08:14:12 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
The documentation referenced the wrong kernel version.
Signed-off-by: Dylan Yudaken <[email protected]>
---
man/io_uring_prep_recv.3 | 2 +-
man/io_uring_prep_recvmsg.3 | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/io_uring_prep_recv.3 b/man/io_uring_prep_recv.3
index 60a77fc241b5..b3862369affa 100644
--- a/man/io_uring_prep_recv.3
+++ b/man/io_uring_prep_recv.3
@@ -55,7 +55,7 @@ If a posted CQE does not have the
.B IORING_CQE_F_MORE
flag set then the multishot receive will be done and the application should issue a
new request.
-Multishot variants are available since kernel 5.20.
+Multishot variants are available since kernel 6.0.
After calling this function, additional io_uring internal modifier flags
diff --git a/man/io_uring_prep_recvmsg.3 b/man/io_uring_prep_recvmsg.3
index 07096ee4826c..65f324dfef9b 100644
--- a/man/io_uring_prep_recvmsg.3
+++ b/man/io_uring_prep_recvmsg.3
@@ -65,7 +65,7 @@ submitted with the request. See
.B io_uring_recvmsg_out (3)
for more information on accessing the data.
-Multishot variants are available since kernel 5.20.
+Multishot variants are available since kernel 6.0.
After calling this function, additional io_uring internal modifier flags
may be set in the SQE
--
2.30.2
next prev parent reply other threads:[~2022-09-26 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 15:14 [PATCH liburing 0/2] 6.0 updates Dylan Yudaken
2022-09-26 15:14 ` [PATCH liburing 1/2] handle single issuer task registration at ring creation Dylan Yudaken
2022-09-26 15:14 ` Dylan Yudaken [this message]
2022-09-26 17:18 ` [PATCH liburing 0/2] 6.0 updates Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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