From: Tony Lindgren <tony@atomide.com>
To: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Bug on "omap: ioremap fixes for omap4"
Date: Mon, 19 Oct 2009 10:12:59 -0700 [thread overview]
Message-ID: <20091019171259.GQ12576@atomide.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89444CEFF1AE@dlee02.ent.ti.com>
* Aguirre Rodriguez, Sergio Alberto <saaguirre@ti.com> [091019 08:54]:
> Tony, Santosh,
>
> I think there's a missing fix in this commit:
>
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=041b80d9a00ab741ce50db92c84b6bed554fc3b6
>
> Here:
>
> > diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c
> > index 50a62f2..4b644a9 100644
> > --- a/arch/arm/mach-omap2/board-4430sdp.c
> > +++ b/arch/arm/mach-omap2/board-4430sdp.c
> > @@ -60,9 +60,9 @@ static void __init gic_init_irq(void)
> > gic_dist_init(0, base, 29);
> >
> > /* Static mapping, never released */
> > - base = ioremap(OMAP44XX_GIC_CPU_BASE, SZ_256);
> > + gic_cpu_base_addr = ioremap(OMAP44XX_GIC_CPU_BASE, SZ_512);
> > BUG_ON(!base);
>
> Shouldn't it be:
>
> BUG_ON(!gic_cpu_base_addr);
>
> Instead?
>
> > - gic_cpu_init(0, OMAP44XX_GIC_CPU_BASE);
> > + gic_cpu_init(0, gic_cpu_base_addr);
> > }
> >
> > static void __init omap_4430sdp_init_irq(void)
Yeah thanks, I've posted a refreshed patch for that
and pushed the fix to linux-omap master and for-next
branches.
Regards,
Tony
prev parent reply other threads:[~2009-10-19 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 15:54 Bug on "omap: ioremap fixes for omap4" Aguirre Rodriguez, Sergio Alberto
2009-10-19 17:12 ` Tony Lindgren [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=20091019171259.GQ12576@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.com \
--cc=santosh.shilimkar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.