On Thu, Nov 12, 2020 at 04:26:10PM -0800, Roman Gushchin wrote: > > These patches are not intended to be merged through the bpf tree. > They are included into the patchset to make bpf selftests pass and for > informational purposes. > It's written in the cover letter. ... > Maybe I had to just list their titles in the cover letter. Idk what's > the best option for such cross-subsystem dependencies. We had several situations in the past releases where dependent patches were merged into multiple trees. For that to happen cleanly from git pov one of the maintainers need to create a stable branch/tag and let other maintainers pull that branch into different trees. This way the sha-s stay the same and no conflicts arise during the merge window. In this case sounds like the first 4 patches are in mm tree already. Is there a branch/tag I can pull to get the first 4 into bpf-next?
