On Wed, Aug 05, 2020 at 07:01:52PM +0000, Saeed Mahameed wrote: > On Wed, 2020-08-05 at 09:12 -0400, Michael S. Tsirkin wrote: > > On Wed, Aug 05, 2020 at 04:01:58PM +0300, Eli Cohen wrote: > > > On Wed, Aug 05, 2020 at 08:48:52AM -0400, Michael S. Tsirkin wrote: > > > > > Did you merge this?: > > > > > git pull > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.gi > > > > > t mlx5-next > > > > > > > > I can only merge this tree if no one else will. Linus does not > > > > like getting same patches through two trees. This is not quite the case Linus does not like multiple *copies* of the same patches. The same actual git commits can be OK. Linus also does not like unnecessarily cross linking trees, mlx5-next is designed to be small enough and approved enough that it is not controversial. Linus really doesn't like it when people jams stuff together in rc7 or the weeks of the merge window. He wants to see stuff be in linux-next for at least a bit. So it may be too late regardless. > We do this all the time with net-next and rdma, > mlx5-next is a very small branch based on a very early rc that includes > mlx5 shared stuff between rdma and net-next, and now virtio as well. Yes, going on two years now? Been working well Jason _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
