From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH NEXT] irqchip: gic: fix compilation of asm code depending on arm-gic.h
Date: Fri, 28 Nov 2014 10:39:09 +0000 [thread overview]
Message-ID: <20141128103908.GB7144@arm.com> (raw)
In-Reply-To: <1417170975-1163-1-git-send-email-marc.zyngier@arm.com>
On Fri, Nov 28, 2014 at 10:36:15AM +0000, Marc Zyngier wrote:
> Commit 01f17a66be97 (irqchip: gic: Remove warning by including
> linux/irqdomain.h) indeed fixed an annoying warning in the ARM
> code, but also broke the compilation of arm64 defconfig and
> any other defconfig that includes KVM support in a rather
> spectacular way:
>
> http://lists.linaro.org/pipermail/kernel-build-reports/2014-November/006475.html
>
> Moving the #include directive to a spot that is not going to
> be used by assembly code fixes the issue.
>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Cc: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
> include/linux/irqchip/arm-gic.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Acked-by: Will Deacon <will.deacon@arm.com>
arm64 allmodconfig is dead in the water without this fix.
Will
> diff --git a/include/linux/irqchip/arm-gic.h b/include/linux/irqchip/arm-gic.h
> index d1b2263..71d706d 100644
> --- a/include/linux/irqchip/arm-gic.h
> +++ b/include/linux/irqchip/arm-gic.h
> @@ -10,8 +10,6 @@
> #ifndef __LINUX_IRQCHIP_ARM_GIC_H
> #define __LINUX_IRQCHIP_ARM_GIC_H
>
> -#include <linux/irqdomain.h>
> -
> #define GIC_CPU_CTRL 0x00
> #define GIC_CPU_PRIMASK 0x04
> #define GIC_CPU_BINPOINT 0x08
> @@ -93,6 +91,8 @@
>
> #ifndef __ASSEMBLY__
>
> +#include <linux/irqdomain.h>
> +
> struct device_node;
>
> extern struct irq_chip gic_arch_extn;
> --
> 2.1.3
>
>
next prev parent reply other threads:[~2014-11-28 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 10:36 [PATCH NEXT] irqchip: gic: fix compilation of asm code depending on arm-gic.h Marc Zyngier
2014-11-28 10:39 ` Will Deacon [this message]
2014-11-28 16:49 ` Jason Cooper
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=20141128103908.GB7144@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).