From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: sh7372 INTCS MFIS2 interrupt update
Date: Tue, 18 Jan 2011 04:50:23 +0000 [thread overview]
Message-ID: <20110118045023.GJ2122@linux-sh.org> (raw)
In-Reply-To: <20100311054221.27152.9839.sendpatchset@t400s>
On Tue, Jan 18, 2011 at 12:13:44PM +0900, Magnus Damm wrote:
> Enable the MFIS2 interrupt source in the INTCS interrupt
> controller included in the sh7372 processor. The priority
> field is constantly enabled to let the interrupt through to
> both the ARM side and the SH side.
On Tue, Jan 18, 2011 at 12:41:04PM +0900, Magnus Damm wrote:
> set_irq_type() should only be used for external IRQ pins,
> so update the G3EVM board code to remove low level request.
Both applied, thanks.
prev parent reply other threads:[~2011-01-18 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 5:42 [PATCH] ARM: mach-shmobile: sh7372 INTCS support Magnus Damm
2010-05-20 3:11 ` Paul Mundt
2011-01-18 3:13 ` [PATCH] ARM: mach-shmobile: sh7372 INTCS MFIS2 interrupt update Magnus Damm
2011-01-18 4:50 ` Paul Mundt [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=20110118045023.GJ2122@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).