On Fri, Jun 30, 2017 at 06:27:17AM +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> On Thu, 29 Jun 2017 13:16:40 -0700 Kees Cook <keescook@chromium.org> wrote:
> >
> > [1] If the solution for this is to merge other -next trees into mine,
> > I guess I can do that, though it can be very messy if any of them are
> > forced to make their commits unstable. It also creates headaches,
> > AIUI, for sfr if my tree suddenly gains a bunch of other trees so it's
> > not clear where something came from.
>
> I don't have a problem with trees in linux-next sharing *commits* - I
> have problems when they share *patches* that are different commits
> (that affect files that get changed in other commits).

Do we have any sane way to overcome this limitation?

I tried to add my tree [1] to participate in linux-next. My tree
includes my submission queue and important patches posted to the mailing list
to the RDMA subsystem.

The absence of ability to add parallel tree with same commits doesn't allow us
effectively test the RDMA patches.

The reasons to it are combination of mostly two factors: my tree is not
official one [2] (all patches in my tree are not officially final) and very
sporadic update very close and/or during merge window [3].

In this cycle, we missed merge window [4] because lack of ready for pull tree [5].

Thanks

[1] https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/
[2] https://git.kernel.org/cgit/linux/kernel/git/dledford/rdma.git/
[3] http://marc.info/?l=linux-next&m=149999488214297&w=2
[4] http://marc.info/?l=linux-rdma&m=149980130008834&w=2
[5] http://marc.info/?l=linux-rdma&m=149987945120683&w=2