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

[Jens Axboe <axboe@kernel.dk>]

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.

-- 
Jens Axboe