From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 04/12] irqchip: nvic: support routable irq domain ops
Date: Wed, 03 Dec 2014 11:49:50 +0100 [thread overview]
Message-ID: <4576226.8jDcZiCptE@wuerfel> (raw)
In-Reply-To: <1417565531-4507-5-git-send-email-stefan@agner.ch>
On Wednesday 03 December 2014 01:12:03 Stefan Agner wrote:
> +#ifdef CONFIG_ARM_NVIC
> +extern const struct irq_domain_ops *nvic_routable_irq_domain_ops;
> +static inline void __init register_routable_domain_ops
> + (const struct irq_domain_ops *ops)
> +{
> + nvic_routable_irq_domain_ops = ops;
> +}
> +#endif /* CONFIG_ARM_NVIC */
>
As you mentioned, this conflicts with the gic specific declaration.
Why not remove the #ifdef here and rename the function to
nvic_register_routable_domain_ops() ?
If that doesn't work, I guess we need something more generic
and move the routable_irq_domain_ops to some common location.
Arnd
next prev parent reply other threads:[~2014-12-03 10:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 0:11 [PATCH 00/12] ARM: vf610m4: Add Vybrid Cortex-M4 support Stefan Agner
2014-12-03 0:12 ` [PATCH 01/12] ARM: dts: vf610: add routable-irqs property for gic node Stefan Agner
2014-12-03 0:12 ` [PATCH 02/12] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM) Stefan Agner
2014-12-03 0:12 ` [PATCH 03/12] irqchip: gic: define register_routable_domain_ops conditional Stefan Agner
2014-12-03 10:46 ` Arnd Bergmann
2014-12-03 13:04 ` Thomas Gleixner
2014-12-03 17:28 ` Stefan Agner
2014-12-03 19:04 ` Marc Zyngier
2014-12-04 0:03 ` Thomas Gleixner
2014-12-04 13:35 ` Stefan Agner
2014-12-04 13:42 ` Marc Zyngier
2014-12-04 13:50 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 04/12] irqchip: nvic: support routable irq domain ops Stefan Agner
2014-12-03 9:39 ` Uwe Kleine-König
2014-12-03 10:49 ` Arnd Bergmann [this message]
2014-12-03 17:32 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 05/12] irqchip: nvic: increase number of external interrupts to 112 Stefan Agner
2014-12-03 8:12 ` Uwe Kleine-König
2014-12-03 17:40 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 06/12] ARM: imx: add support for MSCM interrupt router Stefan Agner
2014-12-03 10:51 ` Arnd Bergmann
2014-12-03 0:12 ` [PATCH 07/12] Documentation: dt: imx: add MSCM documentation Stefan Agner
2014-12-03 10:52 ` Arnd Bergmann
2014-12-03 17:49 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 08/12] clocksource: add dependencies for Vybrid pit clocksource Stefan Agner
2014-12-03 0:12 ` [PATCH 09/12] ARM: unify MMU/!MMU addruart calls Stefan Agner
2014-12-03 10:53 ` Arnd Bergmann
2014-12-03 0:12 ` [PATCH 10/12] ARM: vf610m4: add new machine and SoC for Vybrid on Cortex-M4 Stefan Agner
2014-12-03 10:56 ` Arnd Bergmann
2014-12-03 18:00 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 11/12] ARM: dts: add support for Vybrid running " Stefan Agner
2014-12-03 11:03 ` Arnd Bergmann
2014-12-16 22:19 ` Stefan Agner
2014-12-17 10:57 ` Arnd Bergmann
2014-12-16 23:41 ` Stefan Agner
2014-12-17 12:31 ` Arnd Bergmann
2014-12-18 20:36 ` Stefan Agner
2014-12-18 22:44 ` Arnd Bergmann
2014-12-20 18:49 ` Stefan Agner
2014-12-03 0:12 ` [PATCH 12/12] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4 Stefan Agner
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=4576226.8jDcZiCptE@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