From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] arm: bcm2835: convert to the irqchip infrastructure
Date: Wed, 7 Nov 2012 08:09:52 +0100 [thread overview]
Message-ID: <20121107080952.0594f3ef@skate> (raw)
In-Reply-To: <20121106165639.GF1254@beefymiracle.amer.corp.natinst.com>
Josh,
On Tue, 6 Nov 2012 10:56:39 -0600, Josh Cartwright wrote:
> Could it make sense here to kill the irqchip.h private export, and
> instead rely on the linker to stitch together the builtin irqchip's
> of_device_id tables?
Yes, using yet another ELF section is another option to do that. I just
wasn't sure it was worth the effort for now, but if it is seen as
necessary, I can certainly go ahead and implement this.
I am at ELCE at the moment, so quite busy with talks, discussions...
and drinks. I'll get back to this when I get back from ELCE.
Thanks for your suggestion,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-07 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:19 [PATCH v3] Introduce minimal irqchip infrastructure Thomas Petazzoni
2012-10-28 22:19 ` [PATCH v3 1/4] irqchip: add basic infrastructure Thomas Petazzoni
2012-10-28 22:19 ` [PATCH v3 2/4] arm: bcm2835: convert to the irqchip infrastructure Thomas Petazzoni
2012-11-06 16:56 ` Josh Cartwright
2012-11-06 17:54 ` Josh Cartwright
2012-11-07 7:09 ` Thomas Petazzoni [this message]
2012-10-28 22:19 ` [PATCH v3 3/4] arm: mvebu: move irq controller driver to drivers/irqchip Thomas Petazzoni
2012-10-29 9:18 ` Sebastian Hesselbarth
2012-10-29 9:24 ` Thomas Petazzoni
2012-10-29 9:38 ` Sebastian Hesselbarth
2012-10-29 9:50 ` Thomas Petazzoni
2012-10-29 10:03 ` Andrew Lunn
2012-10-28 22:19 ` [PATCH v3 4/4] irqchip: add to the directories part of the IRQ subsystem in MAINTAINERS Thomas Petazzoni
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=20121107080952.0594f3ef@skate \
--to=thomas.petazzoni@free-electrons.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 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.