From: Chris Ball <cjb@laptop.org>
To: Venkatraman S <svenkatr@ti.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/5] mmc: omap_hsmmc: Few patches for omap_hsmmc
Date: Sat, 17 Nov 2012 20:09:21 -0500 [thread overview]
Message-ID: <87lidz7m4e.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1352220737-14071-1-git-send-email-svenkatr@ti.com> (Venkatraman S.'s message of "Tue, 6 Nov 2012 22:22:11 +0530")
Hi Venkat,
On Tue, Nov 06 2012, Venkatraman S wrote:
> Hi Chris,
> Please review and merge the below patches.
> The first one is a bug fix that would be required to be sent
> for 3.7-rcX, others are intended for 3.8.
There have been some changes requested to these -- could you resend your
3.8 queue to me, please?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-11-18 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 16:52 [PATCH 0/5] mmc: omap_hsmmc: Few patches for omap_hsmmc Venkatraman S
2012-11-06 16:52 ` [PATCH 1/5] mmc: omap_hsmmc: Avoid host->cmd dereference during data transfer failures Venkatraman S
2012-11-09 15:48 ` Balaji T K
2012-11-06 16:52 ` [PATCH 2/5] mmc: omap_hsmmc: Enable HSPE bit for high speed cards Venkatraman S
2012-11-06 16:52 ` [PATCH 3/5] mmc: omap_hsmmc: introduce omap_hsmmc_prepare/complete Venkatraman S
2012-11-06 16:52 ` [PATCH 4/5] mmc: omap_hsmmc: cleanup the bitmap definitions of Interrupt Register Venkatraman S
2012-11-07 13:24 ` Balaji T K
2012-11-08 8:57 ` Venkatraman S
2012-11-06 16:52 ` [PATCH 5/5] mmc: omap_hsmmc: convert critical failure reports to dev_err Venkatraman S
2012-11-18 1:09 ` Chris Ball [this message]
2012-11-19 16:27 ` [PATCH 0/5] mmc: omap_hsmmc: Few patches for omap_hsmmc 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=87lidz7m4e.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--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