public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected],
	[email protected],  [email protected],
	[email protected],  Paul Moore <[email protected]>
Subject: Re: [PATCH v2 0/3] clean up io_uring cmd header structure
Date: Sun, 03 Dec 2023 08:22:20 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Fri, 01 Dec 2023 00:57:34 +0000, Pavel Begunkov wrote:
> Looking at the zc rfc, and how we tend to stuff everything into
> linux/io_uring, start splitting the file before it becomes even more
> monstrous.
> 
> V2: fix up includes for security/
>     Add new files to MAINTAINERS
> 
> [...]

Applied, thanks!

[1/3] io_uring: split out cmd api into a separate header
      (no commit info)
[2/3] io_uring/cmd: inline io_uring_cmd_do_in_task_lazy
      (no commit info)
[3/3] io_uring/cmd: inline io_uring_cmd_get_task
      (no commit info)

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2023-12-03 15:22 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
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 ` 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=170161694061.938645.776262768452153331.b4-ty@kernel.dk \
    [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