Re: [PATCH 1/1] io_uring: move zcrx into a separate branch

[Pavel Begunkov <asml.silence@gmail.com>]

On 8/18/25 16:24, Jens Axboe wrote:
> On 8/17/25 4:43 PM, 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.
> 
> I'm fine with this, as long as it doesn't bifurcate the management of
> the overall/main branch - eg patches will flow from the zcrx branch into
> my main branch, always. I've got many years of experience of managing
> downstream branches with upstream trees, and whenever there are
> dependencies, it's a pain in the butt. Don't want to add to that pain.

That's the assumed workflow. Apart from conflicts I don't want to
deal with, it'll likely be inconsistent and low volume; doesn't
make sense sending it to Linus directly for many reasons.

-- 
Pavel Begunkov