From: Dylan Yudaken <[email protected]>
To: <[email protected]>, <[email protected]>, <[email protected]>
Cc: Dylan Yudaken <[email protected]>, kernel test robot <[email protected]>
Subject: [PATCH for-next] io_uring: fix documentation
Date: Thu, 23 Jun 2022 01:21:54 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
The doc strings were incorrect, fix these up
Reported-by: kernel test robot <[email protected]>
Fixes: c0808632a83a ("io_uring: introduce llist helpers")
Signed-off-by: Dylan Yudaken <[email protected]>
---
Hi,
You may want to just fold this into the original commit.
Dylan
io_uring/io_uring.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index cbbec1cecad3..894652eae449 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -1023,13 +1023,13 @@ static unsigned int handle_tw_list(struct llist_node *node,
* The order of entries returned is from the newest to the oldest added one.
*/
static inline struct llist_node *io_llist_xchg(struct llist_head *head,
- struct llist_node *node)
+ struct llist_node *new)
{
- return xchg(&head->first, node);
+ return xchg(&head->first, new);
}
/**
- * io_llist_xchg - possibly swap all entries in a lock-less list
+ * io_llist_cmpxchg - possibly swap all entries in a lock-less list
* @head: the head of lock-less list to delete all entries
* @old: expected old value of the first entry of the list
* @new: new entry as the head of the list
base-commit: 5ec69c3a15ae6e904d76545d9a9c686eb758def0
--
2.30.2
next reply other threads:[~2022-06-23 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:21 Dylan Yudaken [this message]
2022-06-23 13:59 ` [PATCH for-next] io_uring: fix documentation 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