From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: sh73a0: fixup PINT/IRQ16-IRQ31 irq number conflict
Date: Fri, 18 May 2012 02:55:47 +0000 [thread overview]
Message-ID: <20120518025547.GA26916@verge.net.au> (raw)
In-Reply-To: <87pqa48vrn.wl%kuninori.morimoto.gx@renesas.com>
On Thu, May 17, 2012 at 12:35:42AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, May 16, 2012, Magnus Damm wrote:
> > On Wed, May 16, 2012 at 3:50 PM, Kuninori Morimoto
> > <kuninori.morimoto.gx@renesas.com> wrote:
> > > Current IRQ16-IRQ31 irq number are located around 800 from
> > > 1ee8299a9ec1ce5137a044c7768293007b9a3267
> > > (ARM: mach-shmobile: Use 0x3400 as INTCS vector offset)
> > >
> > > But, the PINT0/1 IRQ number are also located around 800 from
> > > 0df1a838d678fc6ab49f983a19e905f6a42297a0
> > > (ARM: mach-shmobile: sh73a0 PINT IRQ base fix)
> > >
> > > This patch relocates PINT0/1 IRQ number to around 700 where is not used,
> > > and adds current IRQ location table in comment area.
> > >
> > > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > > ---
> > >>> Magnus
> > >
> > > I added IRQ location table on this patch.
> > > Please check it, and please give this patch your acked-by if you can agree this location.
> >
> > Looking good, thanks for this!
> >
> > Acked-by: Magnus Damm <damm@opensource.se>
>
> Applied.
Thanks.
I have verified that this change resolves the problem that I was seeing.
prev parent reply other threads:[~2012-05-18 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 6:50 [PATCH] ARM: mach-shmobile: sh73a0: fixup PINT/IRQ16-IRQ31 irq number conflict Kuninori Morimoto
2012-05-16 6:53 ` Magnus Damm
2012-05-16 22:35 ` Rafael J. Wysocki
2012-05-18 2:55 ` Simon Horman [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=20120518025547.GA26916@verge.net.au \
--to=horms@verge.net.au \
--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).