Re: ioremap bug?

[Kevin Hilman <khilman@deeprootsystems.com>]

"Menon, Nishanth" <nm@ti.com> writes:

> Kevin, Richard,
>> -----Original Message-----
>> From: Menon, Nishanth
> <snip>
>> 
>> > -----Original Message-----
>> > From: Woodruff, Richard
>> > Sent: Thursday, March 12, 2009 9:33 PM
> <snip>
>> >
>> > This rings a bell from a couple months back.  I've not followed the
>> thread
>> > but recall a recent fix to ioremap.
>> >
>> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg08836.html
>> >
>> Ouch.. commit 24f11ec001920f1cfaeeed8e8b55725d900bbb56[1] is what you are
>> speaking of? That commit is not present in pm branch :(
>> 
>
> Aye.. cherry-pick saves the day (yet again).. script runs without a
> hitch.. (though I admire the simple code that Tomi had put for the
> proving the same)..

Thanks, cherry picked into PM branch as well.

> Anyone know of any more similar memory -
> kmalloc/ioremap/dma_alloc_coherent/vm surprises since 2.6.28? ;) but
> that would be pretty lazy me I guess..:D

It's always an exchange.  We get fixes for known bugs, and in exchange
get new bugs that haven't been found yet. ;)

Anyways, PM branch should be moving to 2.6.29 in the next couple
weeks.  Primary hold up is trying to get clock and PM stuff stabilized
and agreed upon for upstream merge (see recent PRCM register access
thread for details.)

Kevin