From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.29.99]:52980 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753610AbeCTOD0 (ORCPT <rfc822;netdev@vger.kernel.org>);
        Tue, 20 Mar 2018 10:03:26 -0400
Date: Tue, 20 Mar 2018 16:03:21 +0200
From: Leon Romanovsky <leon@kernel.org>
To: Steve Wise <swise@opengridcomputing.com>
Cc: 'David Miller' <davem@davemloft.net>, rajur@chelsio.com,
        dledford@redhat.com, linux-rdma@vger.kernel.org, jgg@ziepe.ca,
        netdev@vger.kernel.org, bharat@chelsio.com, ganeshgr@chelsio.com,
        rahul.lakkireddy@chelsio.com
Subject: Re: interdependencies with cxgb4 and iw_cxgb4
Message-ID: <20180320140321.GD19440@mtr-leonro.local>
References: <022f01d3bba9$82e94870$88bbd950$@opengridcomputing.com>
 <20180316.122150.516267509367905206.davem@davemloft.net>
 <2cbb87bf-9020-2788-be75-1dd7f48f6c42@opengridcomputing.com>
 <20180319.193440.1570733225238398675.davem@davemloft.net>
 <01a201d3c051$eebbded0$cc339c70$@opengridcomputing.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="qpPEP5KwiTnADq8L"
Content-Disposition: inline
In-Reply-To: <01a201d3c051$eebbded0$cc339c70$@opengridcomputing.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>


--qpPEP5KwiTnADq8L
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 20, 2018 at 08:47:04AM -0500, Steve Wise wrote:
> > From: Steve Wise <swise@opengridcomputing.com>
> > Date: Mon, 19 Mar 2018 14:50:57 -0500
> >
> > > Let me ask a dumb question:=A0 Why cannot one of the maintaners pull =
the
> > > commit from the other mainainer's git repo directly?=A0 IE why have t=
his
> > > third trusted/signed git repo that has to be on k.o, from which both
> > > maintainers pull?=A0 If one of you can pull it in via a patch series,
> > > like you do for all other patches, and then notify the other
> > > maintainer to pull it from the first maintainers' repo if the series
> > > meets the requirements that it needs to be in both maintainers'
> > > repositories?=A0 This avoids adding more staging git repos on k.o.=A0=
 But
> > > probably I'm missing something...
> >
> > Tree A may not want all of tree B's changes, and vice versa.
>
> I was thinking the special commit would go into a branch that was based o=
n,
> say rc1 or rc2 of one of the maintainers.  Then both maintainers pull that
> into their -next branch.  Would that work?

Steve,

It is more or less what we are doing with our shared PR, we just
"offloaded" the overhead of creating and maintaining that special
branch from maintainers. I don't think that anyone here will say no
to you to create that special branch from time to time.

Thanks

>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--qpPEP5KwiTnADq8L
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkhr/r4Op1/04yqaB5GN7iDZyWKcFAlqxFKkACgkQ5GN7iDZy
WKeEzg//TFWdD/0z4p/B+jgxUCVC3BusbLaIEH2HrTGemOgg4xGrkhFXmBSuLutJ
1/JuZFXvCGj1vaTSWt5OCMhEdKJbxtWmi3LsF4sLt/yYKWM3u7i4Zz6t14k0uzxZ
eFntAD0/okhNRVK+v1eUBlzbhpayR/gA5anQBEP/hZJaImN9xM5quOF0L55ki9Bm
CXW9/a98YzNYi2+jjsb3iTPEJzgD1wT+HHHVwplP5tylJE69rM6W3WnOGQ21o9Zy
YxsI6wGMa0qncaUSgu4aBET0Cq8hNmUlbdREeviAMbMZvR7mQ6q7ULNtaHfk49No
X9HPvBho5vylc2+iUzxelXd01UQufpFcCVzRnAbs8T3h9sDuCtc+gy1budkdr34e
6iTrD+f+bTja94piOcizJvo4ulW063PXNtYPqioV20NEJwhbhqLTI/zWJFVTkcWE
Go17yTg0QQchf1yF0ft02X1ZF89V6abpP3+30LPEp6kVaWwC2arNdnAlaJU5EubZ
3PzFzpha58VrjNlvbljFCUtvxhxFRrpsSNJYujl5uBu4qUygIM2DOJV/xxUj9dEK
ltmx3CT1c15FKizrM2jpI4WpZNYxqeu4XwcRJ+vue/8oGIxceD6FyDBiLsTxAhSo
TajWqztFXAV1BdbxXC2xGk6MAtgzDR6/+HHE5oUSKCrZkBMVJvA=
=uCC4
-----END PGP SIGNATURE-----

--qpPEP5KwiTnADq8L--