[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1492721143.3041.20.camel@redhat.com>
Date: Thu, 20 Apr 2017 16:45:43 -0400
From: Doug Ledford <dledford@...hat.com>
To: Leon Romanovsky <leonro@...lanox.com>
Cc: David Miller <davem@...emloft.net>, saeedm@...lanox.com,
netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
erezsh@...lanox.com, jgunthorpe@...idianresearch.com,
niranjana.vishwanathapura@...el.com
Subject: Re: [PATCH net-next 00/16] Mellanox, mlx5 RDMA net device support
On Thu, 2017-04-20 at 21:49 +0300, Leon Romanovsky wrote:
> On Thu, Apr 20, 2017 at 02:41:17PM -0400, Doug Ledford wrote:
> >
> > On Mon, 2017-04-17 at 11:08 -0400, David Miller wrote:
> > >
> > > From: Saeed Mahameed <saeedm@...lanox.com>
> > > Date: Thu, 13 Apr 2017 06:36:50 +0300
> > >
> > > >
> > > > This series provides the lower level mlx5 support of RDMA
> > > > netdevice
> > > > creation API [1] suggested and introduced by Intel's HFI OPA
> > > > VNIC
> > > > netdevice driver [2], to enable IPoIB mlx5 RDMA netdevice
> > > > creation.
> > >
> > > Series applied to net-next.
> >
> > I've pulled Dave's net-next into a branch in my tree for the IPoIB
> > patches to go on top of so that way it can hold the final touchup
> > patch
> > without any conflicts anywhere.
>
> Thanks,
>
> How and when do you want us to forward it?
The branch in question is already pushed for 0day and linux-next
testing, so you can send the fixup patch to linux-rdma based upon my
k.o/for-4.12-rdma-netdevice branch any time.
--
Doug Ledford <dledford@...hat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Powered by blists - more mailing lists