public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: Ming Lei <[email protected]>
Subject: Re: [PATCH for-next 0/4] clean up io_req_complete_post
Date: Fri, 05 Apr 2024 20:06:48 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Fri, 05 Apr 2024 16:50:01 +0100, Pavel Begunkov wrote:
> Patch 1 from Ming Lei removes a good chunk of unreachable code. Add a
> warning in patch 2, and apparently we can develop on the idea and remove
> even more dead code in patches 3,4.
> 
> Ming Lei (1):
>   io_uring: kill dead code in io_req_complete_post
> 
> [...]

Applied, thanks!

[1/4] io_uring: kill dead code in io_req_complete_post
      (no commit info)
[2/4] io_uring: turn implicit assumptions into a warning
      (no commit info)
[3/4] io_uring: remove async request cache
      (no commit info)
[4/4] io_uring: remove io_req_put_rsrc_locked()
      (no commit info)

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2024-04-06  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 15:50 [PATCH for-next 0/4] clean up io_req_complete_post Pavel Begunkov
2024-04-05 15:50 ` [PATCH for-next 1/4] io_uring: kill dead code in io_req_complete_post Pavel Begunkov
2024-04-05 15:50 ` [PATCH for-next 2/4] io_uring: turn implicit assumptions into a warning Pavel Begunkov
2024-04-06 13:21   ` Ming Lei
2024-04-05 15:50 ` [PATCH for-next 3/4] io_uring: remove async request cache Pavel Begunkov
2024-04-06 13:26   ` Ming Lei
2024-04-05 15:50 ` [PATCH for-next 4/4] io_uring: remove io_req_put_rsrc_locked() Pavel Begunkov
2024-04-06 13:28   ` Ming Lei
2024-04-06  2:06 ` 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=171236920863.2449875.7144685921843197110.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