From: Michael Ellerman <mpe@ellerman.id.au>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] powerpc: export cpu_to_core_id()
Date: Thu, 02 Jun 2016 21:03:13 +1000 [thread overview]
Message-ID: <1464865393.11826.0.camel@ellerman.id.au> (raw)
In-Reply-To: <201606020900.u528tQHH025445@mx0a-001b2d01.pphosted.com>
On Thu, 2016-06-02 at 06:00 -0300, Mauricio Faria de Oliveira wrote:
> Hi Michael,
> On 06/02/2016 04:41 AM, Michael Ellerman wrote:
> > On Wed, 2016-06-01 at 17:16 -0300, Mauricio Faria de Oliveira wrote:
> > > Export cpu_to_core_id(). This will be used by the lpfc driver.
> >
> > Can you explain why?
>
> Yup,
> > I would have thought there'd be architecture neutral APIs you can use - and if
> > there aren't maybe we should write them.
>
> I actually use topology_core_id() from <kernel/topology.h> in lpfc [1]
> (defined to cpu_to_core_id() by arch/powerpc/include/asm/topology.h).
>
> That is arch-neutral, used by eg /sys/devices/system/cpu/cpu*/topology,
> but drivers/base/topology.c is built-in (obj-y in ./Makefile), and thus
> didn't need the export.
>
> Thus, since the module uses topology_core_id() and this is defined to
> cpu_to_core_id(), it needs the export:
>
> ERROR: "cpu_to_core_id" [drivers/scsi/lpfc/lpfc.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
Thanks.
Can you send me a v2 with a change log that includes all that detail.
cheers
next prev parent reply other threads:[~2016-06-02 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 20:16 [PATCH 1/3] powerpc: export cpu_to_core_id() Mauricio Faria de Oliveira
2016-06-01 20:19 ` Mauricio Faria de Oliveira
2016-06-02 7:41 ` Michael Ellerman
2016-06-02 9:00 ` Mauricio Faria de Oliveira
2016-06-02 9:05 ` Mauricio Faria de Oliveira
[not found] ` <201606020900.u528tQHH025445@mx0a-001b2d01.pphosted.com>
2016-06-02 11:03 ` Michael Ellerman [this message]
2016-06-02 11:22 ` Mauricio Faria de Oliveira
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=1464865393.11826.0.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mauricfo@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).