public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Gabriel Krisman Bertazi <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH 0/3] trivial fixes and a cleanup of provided buffers
Date: Thu, 05 Oct 2023 08:38:45 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Wed, 04 Oct 2023 20:05:28 -0400, Gabriel Krisman Bertazi wrote:
> Jens,
> 
> I'm resubmitting the slab conversion for provided buffers with the
> suggestions from Jeff (thanks!) for your consideration, and appended 2
> minor fixes related to kbuf in the patchset. Since the patchset grew
> from 1 to 3 patches, i pretended it is not a v2 and restart the
> counting from 1.
> 
> [...]

Applied, thanks!

[1/3] io_uring: Fix check of BID wrapping in provided buffers
      commit: ab69838e7c75b0edb699c1a8f42752b30333c46f
[2/3] io_uring: Allow the full buffer id space for provided buffers
      commit: f74c746e476b9dad51448b9a9421aae72b60e25f
[3/3] io_uring: Use slab for struct io_buffer objects
      commit: b3a4dbc89d4021b3f90ff6a13537111a004f9d07

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2023-10-05 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  0:05 [PATCH 0/3] trivial fixes and a cleanup of provided buffers Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 1/3] io_uring: Fix check of BID wrapping in " Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 2/3] io_uring: Allow the full buffer id space for " Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 3/3] io_uring: Use slab for struct io_buffer objects Gabriel Krisman Bertazi
2023-10-05  2:18 ` [PATCH 0/3] trivial fixes and a cleanup of provided buffers Jens Axboe
2023-10-05 14:25   ` Gabriel Krisman Bertazi
2023-10-05 14:38 ` 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=169651672501.27738.8320097803547315927.b4-ty@kernel.dk \
    [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