From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
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: Sun, 27 Jul 2025 08:14:15 +0700 [thread overview]
Message-ID: <CAFBCWQLA9XCSmJhDmo17HFV_yvarw3srPPna-hhdvZmSOdNs2A@mail.gmail.com> (raw)
In-Reply-To: <20250727010251.3363627-1-ammarfaizi2@gnuweeb.org>
On Sun, Jul 27, 2025 at 8:02 AM 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
>
> I have verified these two functions are not in liburing-ffi.map.
> I will be more careful next time verifying the FFI map file.
> ]
>
> Hi Jens,
Doh, I missed the To header in v2. Good that it's accessible via the
lore kernel.
--
Ammar Faizi
next prev parent reply other threads:[~2025-07-27 1:14 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 ` Ammar Faizi [this message]
2025-07-27 3:52 ` [PATCH liburing v2 0/3] Manpage updates for iowait toggle feature and one extra FFI fix 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=CAFBCWQLA9XCSmJhDmo17HFV_yvarw3srPPna-hhdvZmSOdNs2A@mail.gmail.com \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox