From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] io_uring: remove io_prep_next_work()
Date: Sat, 29 Feb 2020 13:55:53 -0700 [thread overview]
Message-ID: <4d9c6f63-4031-e622-b44f-8d5bfad232dd@kernel.dk> (raw)
In-Reply-To: <b97698208e565be70ae0afae1851e0964260c3f8.1583006078.git.asml.silence@gmail.com>
On 2/29/20 12:56 PM, Pavel Begunkov wrote:
> io-wq cares about IO_WQ_WORK_UNBOUND flag only while enqueueing, so
> it's useless setting it for a next req of a link. Thus, removed it
> from io_prep_linked_timeout(), and inline the function.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-02-29 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 19:48 [PATCH 1/1] io_uring: remove io_prep_next_work() Pavel Begunkov
2020-02-29 19:56 ` [PATCH v2] " Pavel Begunkov
2020-02-29 20:55 ` 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=4d9c6f63-4031-e622-b44f-8d5bfad232dd@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).