GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Pavel Begunkov <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Linux Kernel Mailing List <[email protected]>
Subject: [PATCH liburing v1 0/2] Fixes for io_uring_for_each_cqe
Date: Fri,  9 Jun 2023 08:54:01 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Jens,

Please consider taking these last-minute fixes for liburing-2.4
release. There are two patches in this series:

## 1. man/io_uring_for_each_cqe: Fix return value, title, and typo

  - Fix the return value. io_uring_for_each_cqe() doesn't return an int.

  - Fix the title, it was io_uring_wait_cqes(), it should be
    io_uring_for_each_cqe().

  - Fix typo: s/io_uring_for_each_cqes/io_uring_for_each_cqe/.

## 2. Explicitly tell it's a macro and add an example

Let the reader directly know that it's not a function, but a macro.
Also, give a simple example of its usage.

Signed-off-by: Alviro Iskandar Setiawan <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---

Ammar Faizi (2):
  man/io_uring_for_each_cqe: Fix return value, title, and typo
  man/io_uring_for_each_cqe: Explicitly tell it's a macro and add an example

 man/io_uring_for_each_cqe.3 | 28 +++++++++++++++++++++++-----
 1 file changed, 23 insertions(+), 5 deletions(-)

base-commit: b4ee3108b93f7e4602430246236d14978abad085
-- 
Ammar Faizi


             reply	other threads:[~2023-06-09  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  1:54 Ammar Faizi [this message]
2023-06-09  1:54 ` [PATCH liburing v1 1/2] man/io_uring_for_each_cqe: Fix return value, title, and typo Ammar Faizi
2023-06-09  1:54 ` [PATCH liburing v1 2/2] man/io_uring_for_each_cqe: Explicitly tell it's a macro and add an example Ammar Faizi
2023-06-09  3:02 ` [PATCH liburing v1 0/2] Fixes for io_uring_for_each_cqe Jens Axboe
2023-06-09  3:02 ` 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] \
    [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