From: Chris Ball <cjb@laptop.org>
To: Balaji T K <balajitk@ti.com>
Cc: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
tony@atomide.com, madhu.cr@ti.com, khilman@ti.com,
b-cousson@ti.com, paul@pwsan.com, kishore.kadiyala@ti.com
Subject: Re: [PATCHv4 0/3] OMAP: HSMMC: cleanup and runtime pm
Date: Sat, 09 Jul 2011 18:30:51 -0400 [thread overview]
Message-ID: <m2d3hjjdd0.fsf@bob.laptop.org> (raw)
In-Reply-To: <1309538376-23260-1-git-send-email-balajitk@ti.com> (Balaji T. K.'s message of "Fri, 1 Jul 2011 22:09:33 +0530")
Hi Balaji,
On Fri, Jul 01 2011, Balaji T K wrote:
> Balaji T K (3):
> MMC: OMAP: HSMMC: Remove lazy_disable
> MMC: OMAP: HSMMC: add runtime pm support
> MMC: OMAP: HSMMC: Remove unused iclk
I've merged these three patches to mmc-next for 3.1 now.
> MMC runtime patch has dependency on
> [PATCH 0/6] OMAP2+: hwmod framework fixes [1]
> for MMC1/MMC2 clock to get ungated after idle in OMAP4.
>
> Without [1] patches, MMC1/MMC2 fails to get detected on OMAP4.
>
> [1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg51457.html
I'm assuming that these patches are going to make their way to Linus via
someone else's tree.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-09 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 16:39 [PATCHv4 0/3] OMAP: HSMMC: cleanup and runtime pm Balaji T K
2011-07-01 16:39 ` [PATCHv4 1/3] MMC: OMAP: HSMMC: Remove lazy_disable Balaji T K
2011-07-01 16:39 ` [PATCHv4 2/3] MMC: OMAP: HSMMC: add runtime pm support Balaji T K
2011-07-08 18:24 ` Kevin Hilman
2011-07-13 9:09 ` Dong, Chuanxiao
2011-07-13 14:59 ` Kevin Hilman
2011-07-13 15:34 ` S, Venkatraman
2011-07-13 15:56 ` Kevin Hilman
2011-07-01 16:39 ` [PATCHv4 3/3] MMC: OMAP: HSMMC: Remove unused iclk Balaji T K
[not found] ` <8762nlzy1d.fsf@ti.com>
[not found] ` <CANrkHUb-i4cQmGzrDjcooZPRvyQLSd0+kqLMA04hGzgVjCT+=A@mail.gmail.com>
2011-07-04 18:05 ` [PATCHv4 0/3] OMAP: HSMMC: cleanup and runtime pm S, Venkatraman
2011-07-05 17:43 ` Kevin Hilman
2011-07-09 22:30 ` Chris Ball [this message]
2011-07-09 22:33 ` Paul Walmsley
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=m2d3hjjdd0.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=b-cousson@ti.com \
--cc=balajitk@ti.com \
--cc=khilman@ti.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.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