From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH for-next 0/2] net fixes
Date: Thu, 6 Oct 2022 14:46:22 -0600 [thread overview]
Message-ID: <266638fb-7406-907d-c537-656bed72fac3@kernel.dk> (raw)
In-Reply-To: <27c5613c-6333-c908-0c73-02904a8e5c37@gmail.com>
On 10/6/22 2:30 PM, Pavel Begunkov wrote:
> On 9/30/22 00:47, Jens Axboe wrote:
>> On Thu, 29 Sep 2022 22:23:17 +0100, Pavel Begunkov wrote:
>>> two extra io_uring/net fixes
>>>
>>> Pavel Begunkov (2):
>>> io_uring/net: don't update msg_name if not provided
>>> io_uring/net: fix notif cqe reordering
>>>
>>> io_uring/net.c | 27 +++++++++++++++++++++------
>>> 1 file changed, 21 insertions(+), 6 deletions(-)
>>>
>>> [...]
>>
>> Applied, thanks!
>
> Hmm, where did these go? Don't see neither in for-6.1
> nor 6.1-late
They are in for-6.1/io_uring with the shas listed here too:
>> [1/2] io_uring/net: don't update msg_name if not provided
>> commit: 6f10ae8a155446248055c7ddd480ef40139af788
>> [2/2] io_uring/net: fix notif cqe reordering
>> commit: 108893ddcc4d3aa0a4a02aeb02d478e997001227
Top of tree, in fact:
https://git.kernel.dk/cgit/linux-block/log/?h=for-6.1/io_uring
--
Jens Axboe
next prev parent reply other threads:[~2022-10-06 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 21:23 [PATCH for-next 0/2] net fixes Pavel Begunkov
2022-09-29 21:23 ` [PATCH for-next 1/2] io_uring/net: don't update msg_name if not provided Pavel Begunkov
2022-09-29 21:23 ` [PATCH for-next 2/2] io_uring/net: fix notif cqe reordering Pavel Begunkov
2022-09-29 23:47 ` [PATCH for-next 0/2] net fixes Jens Axboe
2022-10-06 20:30 ` Pavel Begunkov
2022-10-06 20:46 ` Jens Axboe [this message]
2022-10-06 20:54 ` Pavel Begunkov
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=266638fb-7406-907d-c537-656bed72fac3@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.