On 10/21/24 16:49, Jens Axboe wrote:
On 10/21/24 8:25 AM, Paolo Abeni wrote:
Side notes not specifically related to this patch: I likely got lost in
previous revision, but it's unclear to me which is the merge plan here,
could you please (re-)word it?
In the past when there's been dependencies like this, what we've done
is:
Someone, usually Jakub, sets up a branch with the net bits only. Both
the io_uring tree and netdev-next pulls that in.
With that, then the io_uring tree can apply the io_uring specific
patches on top. And either side can send a pull, won't impact the other
tree.
I like that way of doing it, as it keeps things separate, yet still easy
to deal with for the side that needs further work/patches on top.
Yep, I outlined in one of the comments same thing (should put it into
the cover letter). We'll get a branch with net/ patches on the common
base, so that it can be pulled into net and io-uring trees. Then, we
can deal with io_uring patches ourselves.
--
Pavel Begunkov
