public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] GIC DT binding support
Date: Fri, 21 Oct 2011 10:51:08 +0200	[thread overview]
Message-ID: <4024688.X5RT0XjWMI@wuerfel> (raw)
In-Reply-To: <201110201812.29202.arnd@arndb.de>

On Thursday 20 October 2011 18:12:28 Arnd Bergmann wrote:
> I've now rebased your tree on top of 3.1-rc9 plus the stable branches
> from Russell's tree that I already have as dependencies in arm-soc/for-next
> (devel-stable, smp, debug). This has caused no conflicts for me, but
> that doesn't mean that it's correct. Please check that what I have
> in arm-soc/dt/gic and arm-soc/highbank/soc actually works for you
> and does not contain branches that you don't actually need.

I needed this patch in the end:

8<-----
ARM: gic: fix build error with CONFIG_IRQ_DOMAIN disabled

In file included from arch/arm/mach-msm/timer.c:26:0:
asm/hardware/gic.h:42:50: warning: 'struct device_node' declared inside parameter list [enabled by default]
asm/hardware/gic.h:42:50: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
asm/hardware/gic.h:58:20: error: field 'domain' has incomplete type

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
Ok to apply on top?

diff --git a/arch/arm/include/asm/hardware/gic.h b/arch/arm/include/asm/hardware/gic.h
index 1a776a1..a06c3ac 100644
--- a/arch/arm/include/asm/hardware/gic.h
+++ b/arch/arm/include/asm/hardware/gic.h
@@ -35,6 +35,8 @@
 #ifndef __ASSEMBLY__
 #include <linux/irqdomain.h>
 
+struct device_node;
+
 extern void __iomem *gic_cpu_base_addr;
 extern struct irq_chip gic_arch_extn;
 
@@ -55,7 +57,9 @@ struct gic_chip_data {
 	u32 __percpu *saved_ppi_enable;
 	u32 __percpu *saved_ppi_conf;
 #endif
+#ifdef CONFIG_IRQ_DOMAIN
 	struct irq_domain domain;
+#endif
 	unsigned int gic_irqs;
 };
 #endif

  parent reply	other threads:[~2011-10-21  8:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14  3:01 [GIT PULL] GIC DT binding support Rob Herring
2011-10-14  3:18 ` Shawn Guo
2011-10-18  9:53 ` Domenico Andreoli
2011-10-18 14:50   ` Rob Herring
2011-10-18 14:58     ` Domenico Andreoli
2011-10-18 15:10       ` Rob Herring
2011-10-20 12:48 ` Shawn Guo
2011-10-20 12:50   ` Russell King - ARM Linux
2011-10-20 13:07 ` Arnd Bergmann
2011-10-20 14:34   ` Rob Herring
2011-10-20 16:12     ` Arnd Bergmann
2011-10-20 17:09       ` Rob Herring
2011-10-20 18:56         ` Russell King - ARM Linux
2011-10-20 21:04           ` Arnd Bergmann
2011-10-21 18:33             ` Russell King - ARM Linux
2011-10-21 19:31               ` Arnd Bergmann
2011-10-21 22:25                 ` Russell King - ARM Linux
2011-10-20 21:08           ` Rob Herring
2011-10-20 21:15             ` Russell King - ARM Linux
2011-10-20 21:17             ` Arnd Bergmann
2011-10-21  8:51       ` Arnd Bergmann [this message]
2011-10-21 20:09         ` Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2011-10-24 21:38 Rob Herring
2011-10-28 21:17 ` Rob Herring
2011-10-30 22:39   ` Arnd Bergmann
2011-10-31  0:31   ` Arnd Bergmann
2011-10-31  1:45     ` Rob Herring

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=4024688.X5RT0XjWMI@wuerfel \
    --to=arnd@arndb.de \
    --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