From: Kevin Hilman <khilman@ti.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1)
Date: Thu, 22 Mar 2012 16:12:21 -0700 [thread overview]
Message-ID: <87mx7844dm.fsf@ti.com> (raw)
In-Reply-To: <1332379417-7408-1-git-send-email-tom.leiming@gmail.com> (Ming Lei's message of "Thu, 22 Mar 2012 09:23:37 +0800")
Ming Lei <tom.leiming@gmail.com> writes:
> This patch fixes the oops below[1].
>
> Obviously, the count of "struct irq_chip_generic" instances to be
> allocated and setup should be irq_setup->nr_regs instead of
> irq_setup->nr_regs plus one, so just fix the iterator to avoid
> the oops.
[...]
> ---
> v1:
> -add a bit more description to the changelog as suggested by
> Tero and Kevin.
Thanks for the updated version.
Queuing as a fix for v3.4-rc (branch: for_3.4/fixes/pm)
Kevin
prev parent reply other threads:[~2012-03-22 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 1:23 [PATCH] ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1) Ming Lei
2012-03-22 23:12 ` Kevin Hilman [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=87mx7844dm.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tom.leiming@gmail.com \
--cc=tony@atomide.com \
/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