[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200117141232.GX20978@mellanox.com>
Date: Fri, 17 Jan 2020 14:12:35 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: "santosh.shilimkar@...cle.com" <santosh.shilimkar@...cle.com>,
"David S . Miller" <davem@...emloft.net>
CC: Leon Romanovsky <leonro@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
RDMA mailing list <linux-rdma@...r.kernel.org>,
Hans Westgaard Ry <hans.westgaard.ry@...cle.com>,
Moni Shoua <monis@...lanox.com>,
linux-netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH mlx5-next 00/10] Use ODP MRs for kernel ULPs
On Thu, Jan 16, 2020 at 11:34:18AM -0800, santosh.shilimkar@...cle.com wrote:
> On 1/16/20 5:57 AM, Jason Gunthorpe wrote:
> > On Thu, Jan 16, 2020 at 06:59:29AM +0000, Leon Romanovsky wrote:
> > > > 45 files changed, 559 insertions(+), 256 deletions(-)
> > >
> > > Thanks Santosh for your review.
> > >
> > > David,
> > > Is it ok to route those patches through RDMA tree given the fact that
> > > we are touching a lot of files in drivers/infiniband/* ?
> > >
> > > There is no conflict between netdev and RDMA versions of RDS, but to be
> > > on safe side, I'll put all this code to mlx5-next tree.
> >
> > Er, lets not contaminate the mlx5-next with this..
> >
> > It looks like it applies clean to -rc6 so if it has to be in both
> > trees a clean PR against -rc5/6 is the way to do it.
> >
> > Santos, do you anticipate more RDS patches this cycle?
> >
>
> Not for upcoming merge window afaik.
In this case DaveM, will you ack and we can take it through RDMA?
The RDMA pieces look OK to me, like Santos I have reviewed many
versions of this already..
Thanks,
Jason
Powered by blists - more mailing lists