From: Jarkko Nikula <jhnikula@gmail.com>
To: balbi@ti.com
Cc: OMAP Linux discussion <linux-omap@vger.kernel.org>,
Hema HK <hemahk@ti.com>
Subject: Re: What is missing from musb - linux-omap merge?
Date: Wed, 6 Apr 2011 17:51:38 +0300 [thread overview]
Message-ID: <20110406175138.eb700a7e.jhnikula@gmail.com> (raw)
In-Reply-To: <20110406133439.GH25654@legolas.emea.dhcp.ti.com>
On Wed, 6 Apr 2011 16:34:40 +0300
Felipe Balbi <balbi@ti.com> wrote:
> Hi,
>
> On Wed, Apr 06, 2011 at 04:23:34PM +0300, Jarkko Nikula wrote:
> > Hi
> >
> > I've been trying to hunt why the OMAP3 retention on Nokia N900 went
> > broken in 2.6.39-rc and reason is somewhere around musb code merge with
> > linux-omap code or vise versa.
> >
> > I bisected this into:
>
> I guess it's the missing Hema's patch which should be queued already.
> Here it is:
>
> commit 84cebd52a4b5d590af476869dc5b786fe567c095
> Author: Hema HK <hemahk@ti.com>
> Date: Thu Mar 17 16:11:58 2011 +0530
>
> usb: musb: Fix for merge issue
>
Yeah, that was missing from the commits I was testing but it was in
where I started bisecting and where I noticed the retention issue so
this don't fix it.
> you might also need the one below:
>
> commit ee262c660a855864efa78181cf7b7095b6416098
> Author: Hema HK <hemahk@ti.com>
> Date: Tue Mar 22 16:02:12 2011 +0530
>
> usb: musb: Fix the crash issue during reboot
>
Applies fine to 2.6.39-rc2 but still doesn't fix the retention issue.
--
Jarkko
next prev parent reply other threads:[~2011-04-06 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 13:23 What is missing from musb - linux-omap merge? Jarkko Nikula
2011-04-06 13:34 ` Felipe Balbi
2011-04-06 14:51 ` Jarkko Nikula [this message]
2011-04-06 14:59 ` Kevin Hilman
2011-04-07 9:08 ` Hema Kalliguddi
2011-04-07 10:34 ` Jarkko Nikula
2011-04-07 11:38 ` Felipe Balbi
2011-04-07 12:59 ` Hema Kalliguddi
2011-04-07 13:01 ` Hema Kalliguddi
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=20110406175138.eb700a7e.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=balbi@ti.com \
--cc=hemahk@ti.com \
--cc=linux-omap@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).