From: Jens Axboe <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: Re: [PATCHSET 0/2] Add io_uring socket(2) support
Date: Wed, 13 Apr 2022 10:26:03 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 12 Apr 2022 14:22:38 -0600, Jens Axboe wrote:
> The main motivator here is to allow creating a socket as a direct
> descriptor, similarly to how we do it for the open/accept support.
>
Applied, thanks!
[1/2] net: add __sys_socket_file()
(no commit info)
[2/2] io_uring: add socket(2) support
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-13 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:22 [PATCHSET 0/2] Add io_uring socket(2) support Jens Axboe
2022-04-12 20:22 ` [PATCH 1/2] net: add __sys_socket_file() Jens Axboe
2022-04-13 10:59 ` David Miller
2022-04-12 20:22 ` [PATCH 2/2] io_uring: add socket(2) support Jens Axboe
2022-04-13 16:26 ` 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=164986716390.2022.1994521571584523698.b4-ty@kernel.dk \
[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