From: Chris Ball <cjb@laptop.org>
To: Venkatraman S <svenkatr@ti.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
balajitk@ti.com, balbi@ti.com
Subject: Re: [PATCH 0/8][git pull] mmc: omap: Assorted fixes for 3.4 merge window
Date: Sun, 01 Apr 2012 00:40:45 -0400 [thread overview]
Message-ID: <87hax4kqsy.fsf@laptop.org> (raw)
In-Reply-To: <1331905144-31655-1-git-send-email-svenkatr@ti.com> (Venkatraman S.'s message of "Fri, 16 Mar 2012 19:08:56 +0530")
Hi,
On Fri, Mar 16 2012, Venkatraman S wrote:
> Chris,
> Here are a group of fixes posted by Felipe and Balaji for the
> OMAP hsmmc driver in the past few days.
> I've rebased them to the lastest mmc-next and posted them
> here again. These have also been tested on OMAP4 development platform.
>
> Please feel to apply directly or pull if that's convenient.
>
> Changes since yesterday (v1):-
> Fixed formatting issues as suggested by Felipe
> Marked some patches for stable.
>
> The following changes since commit 5f0390f10c0e9c9c504cdbf4af802252628a2490:
>
> mmc: omap_hsmmc: Avoid a regulator voltage change with dt (2012-03-14 11:33:20 -0400)
>
> are available in the git repository at:
>
> git://github.com/svenkatr/linux.git omap-mmc-pending-for-3.4
>
> for you to fetch changes up to 8d54766b608915035b47616ea564e4e9b4dda29c:
>
> mmc: omap4: hsmmc: fix module re-insertion (2012-03-16 11:38:41 +0530)
I've just rebased mmc-next on top of 3.4-rc1, and now there are many
conflicts against your tree -- please could you resend patches 3-8
against that base? I'll take them for 3.4, and will take patches 1-2
for 3.5.
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-04-01 4:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 13:38 [PATCH 0/8][git pull] mmc: omap: Assorted fixes for 3.4 merge window Venkatraman S
2012-03-16 13:38 ` [PATCH v2 1/8] mmc: omap: Enable Auto CMD12 Venkatraman S
2012-03-16 13:51 ` Felipe Balbi
2012-03-16 14:26 ` S, Venkatraman
2012-03-16 13:38 ` [PATCH v2 2/8] mmc: omap: add DDR support to omap_hsmmc Venkatraman S
2012-03-16 13:38 ` [PATCH v2 3/8] mmc: omap: use runtime put sync in probe error patch Venkatraman S
2012-03-16 13:39 ` [PATCH v2 4/8] mmc: omap: context save after enabling runtime pm Venkatraman S
2012-03-16 13:39 ` [PATCH v2 5/8] mmc: host: omap_hsmmc: trivial cleanups Venkatraman S
2012-03-19 5:57 ` Hebbar, Gururaja
2012-03-19 10:25 ` S, Venkatraman
2012-03-16 13:39 ` [PATCH v2 6/8] mmc: host: omap_hsmmc: make it behave well as a module Venkatraman S
2012-03-16 13:39 ` [PATCH v2 7/8] mmc: host: omap_hsmmc: convert to module_platform_driver Venkatraman S
2012-03-16 13:39 ` [PATCH v2 8/8] mmc: omap4: hsmmc: fix module re-insertion Venkatraman S
2012-04-01 4:40 ` Chris Ball [this message]
2012-04-02 7:52 ` [PATCH 0/8][git pull] mmc: omap: Assorted fixes for 3.4 merge window S, Venkatraman
2012-04-02 9:50 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2012-03-15 14:33 Venkatraman S
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=87hax4kqsy.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@ti.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