From: Kevin Hilman <khilman@deeprootsystems.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv2] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it
Date: Thu, 13 Aug 2009 15:52:13 -0700 [thread overview]
Message-ID: <87d46zcoo2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87prazcq5g.fsf@deeprootsystems.com> (Kevin Hilman's message of "Thu\, 13 Aug 2009 15\:20\:11 -0700")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> Jon Hunter <jon-hunter@ti.com> writes:
>
>> This is version 2 of this patch. I have incorporated the changes
>> recommended by Kevin Hilman.
>>
[...]
>
> Thanks, pushing to PM branch and pm-2.6.29.
>
Just FYI in case you cant find this patch in the PM branch. While
rebasing the PM branch, I grouped this patch along with hwmod and the
MMC reset removal so you wont set it on the tip of the PM branch.
Kevin
next prev parent reply other threads:[~2009-08-13 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 20:46 [PATCHv2] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it Jon Hunter
2009-08-13 22:20 ` Kevin Hilman
2009-08-13 22:52 ` Kevin Hilman [this message]
2009-08-14 17:25 ` Jon Hunter
2009-08-14 18:11 ` Kevin Hilman
2009-08-17 8:13 ` Tony Lindgren
2009-08-18 9:04 ` Kevin Hilman
2009-08-18 9:07 ` 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=87d46zcoo2.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=jon-hunter@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