Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel

[Leon Romanovsky <leon@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]

On Fri, Jul 14, 2017 at 08:43:58AM -0700, James Bottomley wrote:
> On Fri, 2017-07-14 at 18:35 +0300, Leon Romanovsky wrote:
> > On Fri, Jul 14, 2017 at 04:10:57PM +0200, Andrew Lunn wrote:
> > >
> > > >
> > > > The difference in maintainers style between netdev and RDMA
> > > > causes to have long queue
> > > > (100+) of patches posted to the ML [2], which are not cross-
> > > > checked in various CIs.
> > >
> > > It is possible to get 0-day to run against any arbitrary git tree,
> > > if you ask nicely. If same is true for the kernel-ci project. So if
> > > you are willing to do the merge work, you can get it tested.
> >
> > 0-day is checking my tree, so it is not the problem.
> >
> > I don't see how kernel-ci can help me, because RDMA requires special
> > hardware to run it and it usually requires more than two endpoints
> > (servers) connected together.
> >
> > My problem is related to changes in other trees for example netdev,
> > which can break RDMA functionality.
> >
> > Technology wise, there are:
> > 1. RoCE - RDMA over Converged Ethernet - netdev is below RDMA
> > 2. IPoIB - IP over Infiniband - netdev is above RDMA
> > 3. HFI-VNIC - Ethernet over OmniPath - netdev is above RDMA
> > 4. iWARP - RDMA over IP networks
> > e.t.c.
>
> So I think your goal is to get your tree and the one above you (Doug's
> tree) into linux-next without causing a mismerge nightmare?

Yeah, exactly, I acknowledge Doug's work and just want to be sure that
all other tress are not breaking our technology and want to see it as soon as
possible.

In regards, of my submissions, I'm pretty confident with it. The patches are
backed by verification teams and don't got public without approval.

>
> I still didn't get why you can't change workflow to share commits? If
> you can do that, linux-next can be based on both your tree and the one
> above it. You can do this either by you sending pull requests or by you
> basing on the upstream tree and rebasing when the patches are accepted
> (rebase is very good at recognizing and discarding the same patch with
> a different commit id).

1. I would like to send pull requests, but It doesn't depend on me to honor
or not pull request.
2. In my early days, I tried to base on upstream and rebase, but it caused
to emails from Stephen [2], maybe I need to try it again.

[1] http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1302627.html

>
> James



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]