From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] arm: omap: gpio: don't access irq_desc array directly
Date: Wed, 5 Jan 2011 08:47:22 +0200 [thread overview]
Message-ID: <20110105064722.GC2458@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <87r5cs42p1.fsf@ti.com>
On Tue, Jan 04, 2011 at 04:24:58PM -0800, Kevin Hilman wrote:
> Felipe Balbi <balbi@ti.com> writes:
>
> > Instead of accessing the irq_desc array directly
> > we can use irq_to_desc(irq). That will allow us to,
> > if wanted, select SPARSE_IRQ and irq_descs will be
> > added to a radix tree, instead of a array.
> >
> > Signed-off-by: Felipe Balbi <balbi@ti.com>
>
> Can you refresh this one against Tony's omap-for-linus branch. The GPIO
> omap_device/hwmod conversion changed things around a bit and this patch
> doesn't apply.
>
> After that, you can send separately, and I'll queue this one along with
> some other GPIO core fixes for the 2.6.38-rc series after -rc1 comes
> out.
Sure, it's attached to this mail.
--
balbi
next prev parent reply other threads:[~2011-01-05 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 12:02 [PATCH 0/4] ARM IRQ Changes Felipe Balbi
2011-01-04 12:02 ` [PATCH 1/4] arm: omap: gpio: don't access irq_desc array directly Felipe Balbi
2011-01-05 0:24 ` Kevin Hilman
2011-01-05 6:47 ` Felipe Balbi [this message]
2011-01-05 17:11 ` Kevin Hilman
2011-01-04 12:02 ` [PATCH 2/4] arm: Kconfig: remove duplicated GENERIC_HARDIRQS entry Felipe Balbi
2011-01-04 14:00 ` Uwe Kleine-König
2011-01-04 14:09 ` Felipe Balbi
2011-01-04 17:33 ` Russell King - ARM Linux
2011-01-04 20:54 ` Uwe Kleine-König
2011-01-05 6:51 ` Felipe Balbi
2011-01-04 12:02 ` [PATCH 3/4] arm: Kconfig: remove duplicated SPARSE_IRQ entry Felipe Balbi
2011-01-04 12:02 ` [PATCH 4/4] arm: Kconfig: allow OMAP to use sparse IRQ numbering Felipe Balbi
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=20110105064722.GC2458@legolas.emea.dhcp.ti.com \
--to=balbi@ti.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).