public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] Follow up io_uring pull for 6.0-rc6
Date: Sun, 18 Sep 2022 07:03:30 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Nothing really major here, but figured it'd be nicer to just get these
flushed out for -rc6 so that the 6.1 branch will have them as well.
That'll make our lives easier going forward in terms of development,
and avoid trivial conflicts in this area.

- Simple trace rename so that the returned opcode name is consistent
  with the enum definition (Stefan)

- Send zc rsrc request vs notification lifetime fix (Pavel)

Please pull!


The following changes since commit fc7222c3a9f56271fba02aabbfbae999042f1679:

  io_uring/msg_ring: check file type before putting (2022-09-15 11:44:35 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.0-2022-09-18

for you to fetch changes up to 9bd3f728223ebcfef8e9d087bdd142f0e388215d:

  io_uring/opdef: rename SENDZC_NOTIF to SEND_ZC (2022-09-18 06:59:13 -0600)

----------------------------------------------------------------
io_uring-6.0-2022-09-18

----------------------------------------------------------------
Pavel Begunkov (1):
      io_uring/net: fix zc fixed buf lifetime

Stefan Metzmacher (1):
      io_uring/opdef: rename SENDZC_NOTIF to SEND_ZC

 io_uring/net.c   | 16 ++++++++--------
 io_uring/opdef.c |  2 +-
 2 files changed, 9 insertions(+), 9 deletions(-)

-- 
Jens Axboe

             reply	other threads:[~2022-09-18 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 13:03 Jens Axboe [this message]
2022-09-18 16:53 ` [GIT PULL] Follow up io_uring pull for 6.0-rc6 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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