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>,
Christian Mazakas <christian.mazakas@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH liburing v2 0/3] Manpage updates for iowait toggle feature and one extra FFI fix
Date: Sat, 26 Jul 2025 21:52:16 -0600 [thread overview]
Message-ID: <175358833617.901373.6744356763469083521.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250727010251.3363627-1-ammarfaizi2@gnuweeb.org>
On Sun, 27 Jul 2025 08:02:48 +0700, Ammar Faizi wrote:
> [
> v2: Keep using IOURINGINLINE on __io_uring_buf_ring_cq_advance
> because it is in the FFI map file.
>
> Now, only remove `IOURINGINLINE` from these two private helpers:
> - __io_uring_set_target_fixed_file
> - __io_uring_peek_cqe
>
> [...]
Applied, thanks!
[1/3] man: Add `io_uring_set_iowait(3)`
commit: 56116db9c371c6d2574709476ba697c0eee59284
[2/3] man: Add `IORING_ENTER_NO_IOWAIT` flag
commit: 6ce9ab3f928a0959b6959b939c4a7ade652abee9
[3/3] liburing: Don't use `IOURINGINLINE` on private helpers
commit: f2b6fb85b79baf17f2c0ea24a357c652caa2d7ba
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-07-27 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 1:02 [PATCH liburing v2 0/3] Manpage updates for iowait toggle feature and one extra FFI fix Ammar Faizi
2025-07-27 1:02 ` [PATCH liburing v2 1/3] man: Add `io_uring_set_iowait(3)` Ammar Faizi
2025-07-27 1:02 ` [PATCH liburing v2 2/3] man: Add `IORING_ENTER_NO_IOWAIT` flag Ammar Faizi
2025-07-27 1:02 ` [PATCH liburing v2 3/3] liburing: Don't use `IOURINGINLINE` on private helpers Ammar Faizi
2025-07-27 1:14 ` [PATCH liburing v2 0/3] Manpage updates for iowait toggle feature and one extra FFI fix Ammar Faizi
2025-07-27 3:52 ` Jens Axboe [this message]
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=175358833617.901373.6744356763469083521.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=christian.mazakas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.