From: Jens Axboe <[email protected]>
To: Jackie Liu <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v3 2/2] io_uring: keep io_put_req only responsible for release and put req
Date: Fri, 8 Nov 2019 08:11:05 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/8/19 7:47 AM, Jackie Liu wrote:
> We already have io_put_req_find_next to find the next req of the link.
> we should not use the io_put_req function to find them. They should be
> functions of the same level.
I like this cleanup, but it doesn't apply to for-5.5/io_uring-test. This
is where I stage things that are still in testing, then I move them to
for-5.5/io_uring once they are good to go.
I applied patch 1 and pushed it out, can you re-generate this one against
the above branch?
--
Jens Axboe
prev parent reply other threads:[~2019-11-08 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:47 [PATCH v3 1/2] io_uring: reduced function parameter ctx if possible Jackie Liu
2019-11-08 14:47 ` [PATCH v3 2/2] io_uring: keep io_put_req only responsible for release and put req Jackie Liu
2019-11-08 15:11 ` 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 \
[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