From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>
Subject: Re: [GIT PULL] OMAP: PM: one more fix for 3.5-rc
Date: Fri, 6 Jul 2012 03:32:14 -0700 [thread overview]
Message-ID: <20120706103213.GT1122@atomide.com> (raw)
In-Reply-To: <877guhenny.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120705 17:35]:
> Tony,
>
> Hopefully this is the last one.
>
> This one fixes a problem where the CORE power domain does not hit
> retention during suspend. This has been known since v3.5 came out, but
> there has been some discussion about the proper fix. The solution has
> now been agreed upon, so I'd like to see this make it for v3.5-rc.
Thanks pulling into fixes.
Tony
prev parent reply other threads:[~2012-07-06 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 0:30 [GIT PULL] OMAP: PM: one more fix for 3.5-rc Kevin Hilman
2012-07-06 10:32 ` 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=20120706103213.GT1122@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).