From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] io_uring: use labeled array init in io_op_defs
Date: Sat, 18 Jan 2020 13:46:36 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <b23c570236ab4b1f47603e52ef545875ac632df8.1579372106.git.asml.silence@gmail.com>
On 1/18/20 11:35 AM, Pavel Begunkov wrote:
> Don't rely on implicit ordering of IORING_OP_ and explicitly place them
> at a right place in io_op_defs. Now former comments are now a part of
> the code and won't ever outdate.
Looks good to me, thanks. Applied.
--
Jens Axboe
prev parent reply other threads:[~2020-01-18 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 18:35 [PATCH] io_uring: use labeled array init in io_op_defs Pavel Begunkov
2020-01-18 20:46 ` 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] \
[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