From: Jens Axboe <[email protected]>
To: [email protected], [email protected], [email protected]
Cc: [email protected]
Subject: Re: [PATCH liburing] remove recvmsg_multishot
Date: Tue, 05 Jul 2022 08:24:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 4 Jul 2022 07:02:04 -0700, Dylan Yudaken wrote:
> This was not well thought out enough, and has some API concerns. Such as
> how do names and control messages come back in a multishot way.
>
> For now delete the recvmsg API until the kernel API is solid.
>
>
Applied, thanks!
[1/1] remove recvmsg_multishot
commit: 47ccd7c2c74c2c68d1a2821391ecf71be5566918
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-07-05 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 14:02 [PATCH liburing] remove recvmsg_multishot Dylan Yudaken
2022-07-05 14:24 ` 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=165703107446.1916500.9733126504302205431.b4-ty@kernel.dk \
[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