[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160805071441.enq2yascwjtf45u5@c203.arch.suse.de>
Date: Fri, 5 Aug 2016 09:14:41 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Borislav Petkov <bp@...en8.de>
Cc: york sun <york.sun@....com>, Michael Ellerman <mpe@...erman.id.au>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"morbidrsa@...il.com" <morbidrsa@...il.com>,
"oss@...error.net" <oss@...error.net>,
Stuart Yoder <stuart.yoder@....com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Kevin Hao <haokexin@...il.com>,
Andrew Donnellan <andrew.donnellan@....ibm.com>,
Yinghai Lu <yinghai@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Patch v3 01/11] arch/powerpc/pci: Fix compiling error for
mpc85xx_edac
On Fri, Aug 05, 2016 at 09:01:26AM +0200, Borislav Petkov wrote:
> On Fri, Aug 05, 2016 at 04:26:26AM +0000, york sun wrote:
> > I don't have deep knowledge of this driver. What I am trying is to
> > separate the common DDR part and share it with ARM platforms. Along the
> > way, I found the compiling error if build a module. If exposing these
> > functions becomes a concern, I can live without it.
>
> Perhaps you or Johannes could fix this properly to use pci_get_device()
> as the rest of the EDAC drivers do, instead of exporting core PCI
> functions...
I can give it a shot, but I don't have too much spare time atm and no hardware
to test, so it'll have a strong RFC smell attached to it.
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@...e.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Powered by blists - more mailing lists