From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
"oss@buserror.net" <oss@buserror.net>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2] powerpc: allow compiling with GENERIC_MSI_IRQ_DOMAIN
Date: Tue, 18 Jul 2017 11:06:54 +0000 [thread overview]
Message-ID: <596DEB80.6020305@nxp.com> (raw)
In-Reply-To: <87pocyhv4n.fsf@concordia.ellerman.id.au>
Hi Michael,
On 07/18/2017 01:55 PM, Michael Ellerman wrote:
> laurentiu.tudor@nxp.com writes:
>
>> From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>>
>> This allows building powerpc with the GENERIC_MSI_IRQ_DOMAIN
>> Kconfig by enabling the asm-generic msi.h in Kbuild. Without
>> this, there's a compilation error [1] because powerpc, as most
>> arches, doesn't provide an asm/msi.h.
>>
>> [1] In file included from ./include/linux/kvm_host.h:20:0,
>> from ./arch/powerpc/include/asm/kvm_ppc.h:30,
>> from arch/powerpc/kernel/dbell.c:20:
>> ./include/linux/msi.h:195:21: fatal error: asm/msi.h: No such file or di=
rectory
>>
>> Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>> ---
>> v2:
>> - compilation error happens when GENERIC_MSI_IRQ_DOMAIN is enabled and=
not
>> GENERIC_MSI_IRQ, so fix commit msg and title
>
> It looks like the only way powerpc can enable GENERIC_MSI_IRQ_DOMAIN is
> by enabling FSL_MC_BUS ?
>
Yes, i think so. I'm currently working on making FSL_MC_BUS compile=20
multi-arch [1] and that's how i hit this compilation error on ppc.
[1] https://lkml.org/lkml/2017/7/17/415
---
Best Regards, Laurentiu=
next prev parent reply other threads:[~2017-07-18 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:12 [PATCH v2] powerpc: allow compiling with GENERIC_MSI_IRQ_DOMAIN laurentiu.tudor
2017-07-18 10:55 ` Michael Ellerman
2017-07-18 11:06 ` Laurentiu Tudor [this message]
2017-07-27 12:37 ` [v2] " Michael Ellerman
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=596DEB80.6020305@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.