On Fri, Jul 03, 2020 at 09:28:09AM +0300, Leon Romanovsky wrote: > On Thu, Jul 02, 2020 at 02:55:41PM -0300, Jason Gunthorpe wrote: > > On Tue, Jun 23, 2020 at 02:01:03PM +0300, Leon Romanovsky wrote: > > > From: Leon Romanovsky <leonro@xxxxxxxxxxxx> > > > > > > >From Michael, > > > > > > This series handles IPoIB child interface creation with setting > > > interface's HW address. > > > > > > In current implementation, lladdr requested by user is ignored and > > > overwritten. Child interface gets the same GID as the parent interface > > > and a QP number which is assigned by the underlying drivers. > > > > > > In this series we fix this behavior so that user's requested address is > > > assigned to the newly created interface. > > > > > > As specific QP number request is not supported for all vendors, QP > > > number requested by user will still be overwritten when this is not > > > supported. > > > > > > Behavior of creation of child interfaces through the sysfs mechanism or > > > without specifying a requested address, stays the same. > > > > > > Thanks > > > > > > Michael Guralnik (2): > > > net/mlx5: Enable QP number request when creating IPoIB underlay QP > > > RDMA/ipoib: Handle user-supplied address when creating child > > > > Applied to for-next, thanks > > Thanks Jason, > > Won't it better that first patch be applied to mlx5-next in order to > avoid possible merge conflicts? Oops, sure, go ahead please Jason
