From: Chris Ball <cjb@laptop.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH 0/3] Enabling patches for Intel MID SDHCI
Date: Thu, 7 Oct 2010 19:07:30 +0100 [thread overview]
Message-ID: <20101007180730.GB15745@void.printf.net> (raw)
In-Reply-To: <20101004142246.901.37491.stgit@localhost.localdomain>
Hi Alan,
On Mon, Oct 04, 2010 at 03:23:55PM +0100, Alan Cox wrote:
> Try again...
>
> This adds basic support for the Intel MID platform devices. It doesn't include
> the callback stuff to handle some of the errata but I'm trying to verify
> which if any of those make sense outside of Intel before resubmitting that
> bit.
Thanks, applied to mmc-next / queued for 2.6.37.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2010-10-07 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 14:23 [PATCH 0/3] Enabling patches for Intel MID SDHCI Alan Cox
2010-10-04 14:24 ` [PATCH 1/3] sdhci: Allow the probe handler to override slots Alan Cox
2010-10-04 14:24 ` [PATCH 2/3] sdhci: Intel Medfield support Alan Cox
2010-10-04 14:25 ` [PATCH 3/3] sdhci: Add Moorestown devices Alan Cox
2010-10-07 18:07 ` Chris Ball [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=20101007180730.GB15745@void.printf.net \
--to=cjb@laptop.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mmc@vger.kernel.org \
/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