public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ming Lei <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: [email protected], Jens Axboe <[email protected]>,
	[email protected], [email protected],
	[email protected], [email protected],
	Paul Moore <[email protected]>
Subject: Re: [PATCH v2 1/3] io_uring: split out cmd api into a separate header
Date: Sun, 3 Dec 2023 21:45:30 +0800	[thread overview]
Message-ID: <ZWyGepj+F8JgGjmh@fedora> (raw)
In-Reply-To: <7ec50bae6e21f371d3850796e716917fc141225a.1701391955.git.asml.silence@gmail.com>

On Fri, Dec 01, 2023 at 12:57:35AM +0000, Pavel Begunkov wrote:
> linux/io_uring.h is slowly becoming a rubbish bin where we put
> anything exposed to other subsystems. For instance, the task exit
> hooks and io_uring cmd infra are completely orthogonal and don't need
> each other's definitions. Start cleaning it up by splitting out all
> command bits into a new header file.
> 
> Signed-off-by: Pavel Begunkov <[email protected]>

Looks fine,

Reviewed-by: Ming Lei <[email protected]>

Thanks,
Ming


  reply	other threads:[~2023-12-03 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  0:57 [PATCH v2 0/3] clean up io_uring cmd header structure Pavel Begunkov
2023-12-01  0:57 ` [PATCH v2 1/3] io_uring: split out cmd api into a separate header Pavel Begunkov
2023-12-03 13:45   ` Ming Lei [this message]
2023-12-01  0:57 ` [PATCH v2 2/3] io_uring/cmd: inline io_uring_cmd_do_in_task_lazy Pavel Begunkov
2023-12-03 13:47   ` Ming Lei
2023-12-01  0:57 ` [PATCH v2 3/3] io_uring/cmd: inline io_uring_cmd_get_task Pavel Begunkov
2023-12-03 13:47   ` Ming Lei
2023-12-03 15:22 ` [PATCH v2 0/3] clean up io_uring cmd header structure Jens Axboe

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=ZWyGepj+F8JgGjmh@fedora \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [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