From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCH 1/1] io_uring: move zcrx into a separate branch
Date: Fri, 17 Oct 2025 13:37:24 +0100 [thread overview]
Message-ID: <64a4c560-1f81-49da-8421-7bf64bb367a0@gmail.com> (raw)
In-Reply-To: <175571404643.442349.8062239826788948822.b4-ty@kernel.dk>
On 8/20/25 19:20, Jens Axboe wrote:
>
> On Sun, 17 Aug 2025 23:43:14 +0100, Pavel Begunkov wrote:
>> Keep zcrx next changes in a separate branch. It was more productive this
>> way past month and will simplify the workflow for already lined up
>> changes requiring cross tree patches, specifically netdev. The current
>> changes can still target the generic io_uring tree as there are no
>> strong reasons to keep it separate. It'll also be using the io_uring
>> mailing list.
>>
>> [...]
>
> Applied, thanks!
Did it get dropped in the end? For some reason I can't find it.
>
> [1/1] io_uring: move zcrx into a separate branch
> commit: 6d136abdd1bdfce0c7108c8e0af6fd95e3d353ad
>
> Best regards,
--
Pavel Begunkov
next prev parent reply other threads:[~2025-10-17 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 22:43 [PATCH 1/1] io_uring: move zcrx into a separate branch Pavel Begunkov
2025-08-18 15:24 ` Jens Axboe
2025-08-18 16:44 ` Pavel Begunkov
2025-08-20 18:20 ` Jens Axboe
2025-10-17 12:37 ` Pavel Begunkov [this message]
2025-10-20 17:07 ` Jens Axboe
2025-10-20 17:41 ` Pavel Begunkov
2025-10-20 18:01 ` Jens Axboe
2025-10-20 18:34 ` Pavel Begunkov
2025-10-21 13:44 ` Pavel Begunkov
2025-10-21 15:42 ` Jens Axboe
2025-10-21 18:45 ` Pavel Begunkov
2025-10-21 18:46 ` Jens Axboe
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=64a4c560-1f81-49da-8421-7bf64bb367a0@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox