From: Jens Axboe <axboe@kernel.dk>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH liburing v1 0/2] Fixes for io_uring_for_each_cqe
Date: Thu, 8 Jun 2023 21:02:10 -0600 [thread overview]
Message-ID: <2a424ca6-5d5d-5e81-fd3a-b25cdd25c690@kernel.dk> (raw)
In-Reply-To: <20230609015403.3523811-1-ammarfaizi2@gnuweeb.org>
On 6/8/23 7:54 PM, Ammar Faizi wrote:
> 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.
Applied, even though not super critical for release. But this should
be it, I'll announce 2.4 tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2023-06-09 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 1:54 [PATCH liburing v1 0/2] Fixes for io_uring_for_each_cqe Ammar Faizi
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 ` Jens Axboe [this message]
2023-06-09 3:02 ` [PATCH liburing v1 0/2] Fixes for io_uring_for_each_cqe 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 \
--in-reply-to=2a424ca6-5d5d-5e81-fd3a-b25cdd25c690@kernel.dk \
--to=axboe@kernel.dk \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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