[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190704121632.GB3401@mellanox.com>
Date: Thu, 4 Jul 2019 12:16:41 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Greg KH <gregkh@...uxfoundation.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"dledford@...hat.com" <dledford@...hat.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"poswald@...e.com" <poswald@...e.com>,
"mustafa.ismail@...el.com" <mustafa.ismail@...el.com>,
"shiraz.saleem@...el.com" <shiraz.saleem@...el.com>,
Dave Ertman <david.m.ertman@...el.com>,
Andrew Bowers <andrewx.bowers@...el.com>
Subject: Re: [net-next 1/3] ice: Initialize and register platform device to
provide RDMA
On Wed, Jul 03, 2019 at 07:12:50PM -0700, Jeff Kirsher wrote:
> From: Tony Nguyen <anthony.l.nguyen@...el.com>
>
> The RDMA block does not advertise on the PCI bus or any other bus.
> Thus the ice driver needs to provide access to the RDMA hardware block
> via a virtual bus; utilize the platform bus to provide this access.
>
> This patch initializes the driver to support RDMA as well as creates
> and registers a platform device for the RDMA driver to register to. At
> this point the driver is fully initialized to register a platform
> driver, however, can not yet register as the ops have not been
> implemented.
I think you need Greg's ack on all this driver stuff - particularly
that a platform_device is OK.
Jason
Powered by blists - more mailing lists