public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 6.19-final
Date: Thu, 5 Feb 2026 15:22:54 -0700	[thread overview]
Message-ID: <1a5a4c44-e073-43e1-8eec-59d8c3bac2b4@kernel.dk> (raw)

Hi Linus,

A set of small fixes that should go into the final release of the 6.19
kernel. This pull request contains:

- Two small fixes for zcrx

- Two small fixes for fdinfo, where one is just killing a superflous
  newline.

Please pull!


The following changes since commit 145e0074392587606aa5df353d0e761f0b8357d5:

  selftests/io_uring: support NO_SQARRAY in miniliburing (2026-01-21 07:55:13 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.19-20260205

for you to fetch changes up to 38cfdd9dd279473a73814df9fd7e6e716951d361:

  io_uring/fdinfo: be a bit nicer when looping a lot of SQEs/CQEs (2026-02-03 10:58:32 -0700)

----------------------------------------------------------------
io_uring-6.19-20260205

----------------------------------------------------------------
Jens Axboe (2):
      io_uring/fdinfo: kill unnecessary newline feed in CQE32 printing
      io_uring/fdinfo: be a bit nicer when looping a lot of SQEs/CQEs

Pavel Begunkov (2):
      io_uring/zcrx: fix page array leak
      io_uring/zcrx: fix rq flush locking

 io_uring/fdinfo.c | 13 +++++++++----
 io_uring/zcrx.c   |  9 +++++----
 2 files changed, 14 insertions(+), 8 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-02-05 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 22:22 Jens Axboe [this message]
2026-02-05 23:34 ` [GIT PULL] io_uring fixes for 6.19-final pr-tracker-bot

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=1a5a4c44-e073-43e1-8eec-59d8c3bac2b4@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=torvalds@linux-foundation.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