From: Jens Axboe <[email protected]>
To: Jakub Kicinski <[email protected]>
Cc: Linus Torvalds <[email protected]>,
io-uring <[email protected]>,
Olivier Langlois <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 5.18-rc1
Date: Wed, 30 Mar 2022 18:44:46 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/30/22 5:30 PM, Jakub Kicinski wrote:
> On Sat, 26 Mar 2022 14:30:49 -0700 Jakub Kicinski wrote:
>> In any case, let's look in detail on Monday :)
>
> I have too many questions, best if we discuss this over the code.
>
> Can we get the change reverted and cross-posted to netdev?
I'm not going to revert this upfront, but I can certainly start
a discussion on netdev so we can poke at it. If we end up
deciding that the API definitely needs to change, then by all
means we'll revert it before 5.18-final. So far it all seems a
bit handwavy to me, so let's discuss it.
--
Jens Axboe
next prev parent reply other threads:[~2022-03-31 0:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 21:59 [GIT PULL] io_uring updates for 5.18-rc1 Jens Axboe
2022-03-22 0:25 ` pr-tracker-bot
2022-03-26 19:28 ` Jakub Kicinski
2022-03-26 19:47 ` Jens Axboe
2022-03-26 20:06 ` Jakub Kicinski
2022-03-26 20:57 ` Jens Axboe
2022-03-26 21:06 ` Jens Axboe
2022-03-26 21:30 ` Jakub Kicinski
2022-03-30 23:30 ` Jakub Kicinski
2022-03-31 0:44 ` Jens Axboe [this message]
2022-06-01 6:59 ` Olivier Langlois
2022-06-01 16:24 ` Jakub Kicinski
2022-06-01 18:09 ` Linus Torvalds
2022-06-01 18:21 ` Jens Axboe
2022-06-01 18:28 ` Linus Torvalds
2022-06-01 18:34 ` Jens Axboe
2022-06-01 18:52 ` Linus Torvalds
2022-06-01 19:10 ` Jens Axboe
2022-06-01 19:20 ` Linus Torvalds
2022-08-16 15:53 ` Deprecation of IORING_OP_EPOLL_CTL (Re: [GIT PULL] io_uring updates for 5.18-rc1) Stefan Metzmacher
2022-06-01 8:01 ` [GIT PULL] io_uring updates for 5.18-rc1 Olivier Langlois
2022-06-01 6:58 ` Olivier Langlois
2022-06-01 6:58 ` Olivier Langlois
2022-06-01 17:04 ` Jakub Kicinski
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] \
[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