From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] Cragganmore updates for 3.3
Date: Thu, 1 Dec 2011 11:37:23 +0000 [thread overview]
Message-ID: <20111201113722.GE2915@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <047301ccb014$273745b0$75a5d110$%kim@samsung.com>
On Thu, Dec 01, 2011 at 07:29:49PM +0900, Kukjin Kim wrote:
> And as a note, I'm thinking about the handling of different
> IRQ_BOARD_NR...but I'm not sure it is really needed or not :)
Yeah, it's annoying. I believe that converting to sparse IRQs would
avoid the issue.
prev parent reply other threads:[~2011-12-01 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 13:30 [PATCH 0/7] Cragganmore updates for 3.3 Mark Brown
2011-11-29 13:30 ` [PATCH 1/7] ARM: S3C64XX: Raise the frequency of the second I2C bus on Cragganmore Mark Brown
2011-11-29 13:30 ` [PATCH 2/7] ARM: S3C64XX: Use software initiated powerdown for Cragganmore Mark Brown
2011-11-29 13:30 ` [PATCH 3/7] ARM: S3C64XX: Configure WM1250 EV1 GPIOs on Cragganmore Mark Brown
2011-11-29 13:30 ` [PATCH 4/7] ARM: S3C64XX: Improve logging of unknown Cragganmore module types Mark Brown
2011-11-29 13:30 ` [PATCH 5/7] ARM: S3C64XX: Run Tobermory interrupts in the default mode Mark Brown
2011-11-29 13:30 ` [PATCH 6/7] ARM: S3C64XX: Hook up platform data for Kilchomin module on Cragganmore Mark Brown
2011-11-29 13:30 ` [PATCH 7/7] ARM: S3C64XX: Hook up Littlemill audio card " Mark Brown
2011-12-01 10:29 ` [PATCH 0/7] Cragganmore updates for 3.3 Kukjin Kim
2011-12-01 11:37 ` Mark Brown [this message]
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=20111201113722.GE2915@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).