From: Breno Leitao <[email protected]>
To: [email protected], [email protected]
Cc: [email protected]
Subject: [PATCH 4/5] man/io_uring_prep_cmd: Fix argument name
Date: Fri, 20 Oct 2023 06:39:16 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
io_uring_prep_cmd(3) documents that one of the argument is SIOCOUTQ,
while, in fact, it is called `SOCKET_URING_OP_SIOCOUTQ`.
Fix the argument name, by replacing SIOCOUTQ to
SOCKET_URING_OP_SIOCOUTQ.
Fixes: 2459fef09411 ("io_uring_prep_cmd: Create a new helper for command ops")
Signed-off-by: Breno Leitao <[email protected]>
---
man/io_uring_prep_cmd.3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/io_uring_prep_cmd.3 b/man/io_uring_prep_cmd.3
index 01b48da..d6ec909 100644
--- a/man/io_uring_prep_cmd.3
+++ b/man/io_uring_prep_cmd.3
@@ -55,7 +55,7 @@ For more information about this command, please check
.TP
-.B SIOCOUTQ
+.B SOCKET_URING_OP_SIOCOUTQ
Returns the amount of unsent data in the socket send queue.
The socket must not be in LISTEN state, otherwise an error
.B -EINVAL
--
2.34.1
next prev parent reply other threads:[~2023-10-20 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 13:39 [PATCH 0/5] liburing: Add {g,s}etsockopt command support Breno Leitao
2023-10-20 13:39 ` [PATCH 1/5] io_uring: uapi: Sync the {g,s}etsockopt fields Breno Leitao
2023-10-20 13:39 ` [PATCH 2/5] liburing.h: Populate SQE for {s,g} etsockopt Breno Leitao
2023-10-20 13:39 ` [PATCH 3/5] tests/socket-getsetsock-cmd: New test for {g,s}etsockopt Breno Leitao
2023-10-20 13:39 ` Breno Leitao [this message]
2023-10-20 13:39 ` [PATCH 5/5] man/io_uring_prep_cmd: Add the new sockopt commands Breno Leitao
2023-10-20 15:06 ` [PATCH 0/5] liburing: Add {g,s}etsockopt command support 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] \
/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