public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	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: [PATCH liburing 0/2] liburing fixes
Date: Sat, 26 Jul 2025 00:59:11 +0700	[thread overview]
Message-ID: <20250725175913.2598891-1-ammarfaizi2@gnuweeb.org> (raw)

Hi Jens,

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.

Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---

Ammar Faizi (2):
  sanitize: Fix missing `IORING_OP_PIPE`
  liburing: Don't use `IOURINGINLINE` on `__io_uring_prep_poll_mask`

 src/include/liburing.h | 2 +-
 src/sanitize.c         | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)


base-commit: ec856cecab2ed4bcbdba2b06a8c7cb5a52083c28
-- 
Ammar Faizi


             reply	other threads:[~2025-07-25 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 17:59 Ammar Faizi [this message]
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 ` [PATCH liburing 0/2] liburing fixes 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=20250725175913.2598891-1-ammarfaizi2@gnuweeb.org \
    --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 \
    --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