From: Borislav Petkov <bp@alien8•de>
To: york sun <york.sun@nxp•com>, Johannes Thumshirn <jthumshirn@suse•de>
Cc: Michael Ellerman <mpe@ellerman•id.au>,
"linux-edac@vger•kernel.org" <linux-edac@vger•kernel.org>,
"morbidrsa@gmail•com" <morbidrsa@gmail•com>,
"oss@buserror•net" <oss@buserror•net>,
Stuart Yoder <stuart.yoder@nxp•com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>, Kevin Hao <haokexin@gmail•com>,
Andrew Donnellan <andrew.donnellan@au1•ibm.com>,
Yinghai Lu <yinghai@kernel•org>,
Bjorn Helgaas <bhelgaas@google•com>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: [Patch v3 01/11] arch/powerpc/pci: Fix compiling error for mpc85xx_edac
Date: Fri, 5 Aug 2016 09:01:26 +0200 [thread overview]
Message-ID: <20160805070126.GE25630@nazgul.tnic> (raw)
In-Reply-To: <AM4PR0401MB17321DA6630E78AF2ED7DA269A180@AM4PR0401MB1732.eurprd04.prod.outlook.com>
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...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-08-05 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1470351518-22404-1-git-send-email-york.sun@nxp.com>
2016-08-04 22:58 ` [Patch v3 01/11] arch/powerpc/pci: Fix compiling error for mpc85xx_edac York Sun
2016-08-04 23:36 ` Andrew Donnellan
2016-08-04 23:39 ` york sun
2016-08-05 6:58 ` Borislav Petkov
2016-08-05 3:43 ` Michael Ellerman
2016-08-05 4:26 ` york sun
2016-08-05 7:01 ` Borislav Petkov [this message]
2016-08-05 7:14 ` Johannes Thumshirn
2016-08-08 15:47 ` york sun
2016-08-05 20:29 ` york sun
2016-08-05 21:09 ` Scott Wood
2016-08-05 21:20 ` york sun
2016-08-05 21:57 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160805070126.GE25630@nazgul.tnic \
--to=bp@alien8$(echo .)de \
--cc=andrew.donnellan@au1$(echo .)ibm.com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=bhelgaas@google$(echo .)com \
--cc=haokexin@gmail$(echo .)com \
--cc=jthumshirn@suse$(echo .)de \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=morbidrsa@gmail$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=oss@buserror$(echo .)net \
--cc=paulus@samba$(echo .)org \
--cc=stuart.yoder@nxp$(echo .)com \
--cc=yinghai@kernel$(echo .)org \
--cc=york.sun@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox