From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: bump up NR_IRQS to 640
Date: Thu, 20 May 2010 03:12:36 +0000 [thread overview]
Message-ID: <20100520031236.GC6661@linux-sh.org> (raw)
In-Reply-To: <20100311053352.26717.21158.sendpatchset@t400s>
On Thu, Mar 11, 2010 at 02:33:52PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> Increase NR_IRQS to 640 on SH-Mobile ARM. With this
> applied the INTCS controller on sh7372 can be supported.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
I've dropped this one due to the INTCS_VECT_BASE shifting, feel free to
resubmit an updated version once support for 10-bit hardirqs hits
upstream.
next prev parent reply other threads:[~2010-05-20 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 5:33 [PATCH] ARM: mach-shmobile: bump up NR_IRQS to 640 Magnus Damm
2010-05-20 3:12 ` Paul Mundt [this message]
2010-12-20 10:56 ` [PATCH] ARM: mach-shmobile: Bump up NR_IRQS to 1024 Magnus Damm
2010-12-20 13:45 ` Paul Mundt
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=20100520031236.GC6661@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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).