[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1488854653.2997.1.camel@sandisk.com>
Date: Tue, 7 Mar 2017 02:44:28 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "parav@...lanox.com" <parav@...lanox.com>,
"dledford@...hat.com" <dledford@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"sebott@...ux.vnet.ibm.com" <sebott@...ux.vnet.ibm.com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>
Subject: Re: [PATCH 1/2] device: Stop requiring that struct device is
embedded in struct pci_dev
On Tue, 2017-03-07 at 02:41 +0000, Parav Pandit wrote:
> Compilation would break when CONFIG_PCI is not defined for some embedded platforms.
> More than that, including specific pci_dev structure pointer in generic structure such as device just doesn't sound right.
> I tested equivalent patch that you sent, but I don't think this is right direction to fix this bug.
You are welcome to voice your opinion. But unless anyone proposes a better
alternative I propose to proceed with this approach.
Bart.
Powered by blists - more mailing lists