From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"Guzman Lugo, Fernando" <x0095840@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Kanigeri, Hari" <h-kanigeri2@ti.com>,
"Lakhani, Amish" <amish@ti.com>, "Gupta, Ramesh" <grgupta@ti.com>,
Ameya Palande <ameya.palande@nokia.com>
Subject: Re: ioremap bug?
Date: Thu, 12 Mar 2009 14:27:55 -0700 [thread overview]
Message-ID: <87fxhi5t44.fsf@deeprootsystems.com> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162037B7D2E7E@dlee02.ent.ti.com> (Richard Woodruff's message of "Thu\, 12 Mar 2009 14\:32\:53 -0500")
"Woodruff, Richard" <r-woodruff2@ti.com> writes:
>> Kevin,
>> Some more isolation:
>> The l-o master branch does not have an issue, only the pm branch seems to have
>> the problem - probably some commit(s?) missing in pm branch. Since bridge is
>> based off the pm branch, wont make sense to regress on it :(.
>
> 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
>
Yes, I was trying to remember why this sounded familiar, thanks
Richard.
The reason it works on l-o and not PM branch is because PM branch is
still 2.6.8 based, and l-o is on 2.6.29-rc which has a fix for this.
Nishant, can you try to cherry-pick commit
24f11ec001920f1cfaeeed8e8b55725d900bbb56 from Linus' tree into your PM
branch and see if that helps.
Kevin
next prev parent reply other threads:[~2009-03-12 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 0:03 DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak Guzman Lugo, Fernando
2009-03-12 16:39 ` ioremap bug? (was RE: DSPBRIDGE: segmentation fault after reloading dspbridge several times due to a memory leak.) Menon, Nishanth
2009-03-12 16:53 ` Menon, Nishanth
2009-03-12 16:58 ` Menon, Nishanth
2009-03-12 17:20 ` Guzman Lugo, Fernando
2009-03-12 17:27 ` Kevin Hilman
2009-03-12 17:49 ` Alejandro Blanca G.
2009-03-12 19:12 ` Menon, Nishanth
2009-03-12 19:32 ` Woodruff, Richard
2009-03-12 21:19 ` Menon, Nishanth
2009-03-12 21:27 ` Kevin Hilman [this message]
2009-03-12 21:49 ` Menon, Nishanth
2009-03-12 22:27 ` ioremap bug? Kevin Hilman
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=87fxhi5t44.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=ameya.palande@nokia.com \
--cc=amish@ti.com \
--cc=grgupta@ti.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=r-woodruff2@ti.com \
--cc=x0095840@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox