From: Jens Axboe <axboe@kernel.dk>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
Christian Mazakas <christian.mazakas@gmail.com>,
Michael de Lang <michael@volt-software.nl>,
io-uring Mailing List <io-uring@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH liburing 0/2] liburing fixes
Date: Fri, 25 Jul 2025 12:21:28 -0600 [thread overview]
Message-ID: <175346768877.681403.14218875042208173659.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250725175913.2598891-1-ammarfaizi2@gnuweeb.org>
On Sat, 26 Jul 2025 00:59:11 +0700, Ammar Faizi wrote:
> Hopefully, not too late for 2.12. Two small final fixes here:
>
> - Fix build error when using address sanitizer due to missing
> `IORING_OP_PIPE` in `sanitize.c`.
>
> - Don't use `IOURINGINLINE` on `__io_uring_prep_poll_mask` as it
> is not a function that should be exported in the FFI API.
>
> [...]
Applied, thanks!
[1/2] sanitize: Fix missing `IORING_OP_PIPE`
commit: ed54d3b7e324220f70dac48b83df4e61763bf844
[2/2] liburing: Don't use `IOURINGINLINE` on `__io_uring_prep_poll_mask`
commit: 6d3d27bc42733f5a407424c76aadcc84bd4b0cf0
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-07-25 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 17:59 [PATCH liburing 0/2] liburing fixes Ammar Faizi
2025-07-25 17:59 ` [PATCH liburing 1/2] sanitize: Fix missing `IORING_OP_PIPE` Ammar Faizi
2025-07-25 17:59 ` [PATCH liburing 2/2] liburing: Don't use `IOURINGINLINE` on `__io_uring_prep_poll_mask` Ammar Faizi
2025-07-25 18:21 ` 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=175346768877.681403.14218875042208173659.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 \
--cc=michael@volt-software.nl \
/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