From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: kzm9g: bugfix: correct mmcif interrupt settings
Date: Tue, 18 Sep 2012 02:24:37 +0000 [thread overview]
Message-ID: <20120918022433.GA11172@verge.net.au> (raw)
In-Reply-To: <1346915976-14079-1-git-send-email-koba@kmckk.co.jp>
On Thu, Sep 06, 2012 at 05:47:14PM -0700, Kuninori Morimoto wrote:
>
> Hi Kobayshi-san
>
> > From: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
> >
> > Correct interrupt settings of sh_mmc:int and sh_mmc:error in board-kzm9g.c.
> >
> > Signed-off-by: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
> > ---
> > Hello, morimoto-san
> >
> > I found small bug in interrpt setting of sh_mmc in board-kzm9g.c.
> > According to SoC document, there are 2 interrupts for sh_mmc and smaller vector id is error. But the setting in board-kzm9g seems wrong.
> >
> > Actually these 2 interrupts use the same interrupt handler. So this patch only affects the output of /proc/interrpts.
> >
> > before this patch:
> > ...
> > 172: 3 0 GIC sh_mmc:int
> > 173: 9504 0 GIC sh_mmc:error
> > ...
> >
> > after this patch:
> > ...
> > 172: 3 0 GIC sh_mmc:error
> > 173: 9454 0 GIC sh_mmc:int
> > ...
> >
> > Morimoto-san, could you verify this?
>
> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Thanks, applied to fixes.
I will try and get this included in 3.6.
next prev parent reply other threads:[~2012-09-18 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 7:19 [PATCH] ARM: shmobile: kzm9g: bugfix: correct mmcif interrupt settings Tetsuyuki Kobayshi
2012-09-07 0:47 ` Kuninori Morimoto
2012-09-18 2:24 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-18 4:46 [GIT PULL] Renesas ARM-based SoC fix for v3.6 #3 Simon Horman
2012-09-18 4:46 ` [PATCH] ARM: shmobile: kzm9g: bugfix: correct mmcif interrupt settings Simon Horman
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=20120918022433.GA11172@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).