From: Tony Lindgren <tony@atomide.com>
To: Chris Ball <cjb@laptop.org>
Cc: Eliad Peller <eliad@wizery.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mmc@vger.kernel.org, Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 1/3] omap_hsmmc: consider MMC_PM_KEEP_POWER on suspend/resume
Date: Thu, 8 Dec 2011 16:28:37 -0800 [thread overview]
Message-ID: <20111209002837.GF31337@atomide.com> (raw)
In-Reply-To: <87r50okviy.fsf@laptop.org>
* Chris Ball <cjb@laptop.org> [111201 09:40]:
> Hi,
>
> On Tue, Nov 22 2011, Eliad Peller wrote:
> > When an mmc card has the MMC_PM_KEEP_POWER flag, it shouldn't
> > be powered off on suspend (and thus doesn't have to be powered-on
> > on resume)
> >
> > While on it, change the suspend flow a bit, to make it a bit
> > easier to follow.
> >
> > Signed-off-by: Eliad Peller <eliad@wizery.com>
>
> Tony, feel free to merge this patchset (if you're happy with the rest of
> it) through your tree, with my:
>
> Acked-by: Chris Ball <cjb@laptop.org>
>
> for this patch. Thanks,
Thanks applying these into omap driver branch.
Regards,
Tony
prev parent reply other threads:[~2011-12-09 0:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:02 [PATCH 1/3] omap_hsmmc: consider MMC_PM_KEEP_POWER on suspend/resume Eliad Peller
2011-11-22 14:02 ` [PATCH 2/3] omap_hsmmc: add pm_caps field Eliad Peller
2011-11-28 9:15 ` Igor Grinberg
2011-11-28 9:23 ` Eliad Peller
2011-11-28 10:01 ` Igor Grinberg
2011-11-28 10:07 ` Eliad Peller
2011-11-28 10:39 ` Igor Grinberg
2011-11-22 14:02 ` [PATCH 3/3] omap: board-sdp4430: declare support for MMC_PM_KEEP_POWER Eliad Peller
2011-11-28 7:50 ` Coelho, Luciano
2011-11-28 8:26 ` Eliad Peller
2011-11-28 9:08 ` Luciano Coelho
2011-11-28 9:26 ` Igor Grinberg
2011-11-28 9:58 ` Luciano Coelho
2011-11-28 10:12 ` Eliad Peller
2011-11-28 10:18 ` Luciano Coelho
2011-12-01 18:16 ` [PATCH 1/3] omap_hsmmc: consider MMC_PM_KEEP_POWER on suspend/resume Chris Ball
2011-12-09 0:28 ` 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=20111209002837.GF31337@atomide.com \
--to=tony@atomide.com \
--cc=cjb@laptop.org \
--cc=eliad@wizery.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).