From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: R8A7779: use gic_iid() in SATA IRQ resource
Date: Fri, 8 Mar 2013 06:33:54 +0100 [thread overview]
Message-ID: <20130308053345.GA771@verge.net.au> (raw)
In-Reply-To: <87obeuahg5.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Mar 07, 2013 at 04:00:46PM -0800, Kuninori Morimoto wrote:
>
> Hi Sergei
>
> > Commit "ARM: shmobile: r8a7779: use gic_iid macro" switched R8A7779 platform
> > devices to using gic_iid() macro instead of gic_spi() but commit "ARM: mach-
> > shmobile: r8a7779: add SATA support" added another use of gic_spi(). Convert
> > the SATA IRQ resource to using gic_iid().
> >
> > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Thanks, I have applied this to the soc5 branch and thus queued it
up for v3.10.
prev parent reply other threads:[~2013-03-08 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 23:31 [PATCH] ARM: shmobile: R8A7779: use gic_iid() in SATA IRQ resource Sergei Shtylyov
2013-03-08 0:00 ` Kuninori Morimoto
2013-03-08 5:33 ` 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=20130308053345.GA771@verge.net.au \
--to=horms@verge.net.au \
--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).