From: Chris Ball <chris@printf.net>
To: Dong Aisheng <dongas86@gmail.com>
Cc: David Cohen <david.a.cohen@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
gregkh <gregkh@linuxfoundation.org>,
"linux-mmc\@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chuanxiao.dong" <chuanxiao.dong@intel.com>
Subject: Re: [RFC/PATCH 0/2] mmc: sdhci: Workaround Intel Merrifield issue for HS200
Date: Mon, 13 Jan 2014 17:55:17 +0000 [thread overview]
Message-ID: <86bnzfdawq.fsf@void.printf.net> (raw)
In-Reply-To: <CAA+hA=SApxYn2=orNz8ZEF-uz7TQ8VBrbLcx6Ozzfd+zNuLCFQ@mail.gmail.com> (Dong Aisheng's message of "Fri, 20 Dec 2013 11:32:07 +0800")
Hi David, Dong,
On Fri, Dec 20 2013, Dong Aisheng wrote:
> On Fri, Dec 20, 2013 at 11:25 AM, David Cohen
> <david.a.cohen@linux.intel.com> wrote:
>> Merrifield still needs this quirk to not break MMC support.
>> This quirk could be applied to 3.13-rc (since merrifield was added to
>> sdhci-pci.c on 3.13-rc1).
>
> Okay, thanks for the information.
> So please take my ACK:
> Acked-by: Dong Aisheng <b29396@freescale.com>
Thanks, I've pushed this to mmc-next now.
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
prev parent reply other threads:[~2014-01-13 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 17:58 [RFC/PATCH 0/2] mmc: sdhci: Workaround Intel Merrifield issue for HS200 David Cohen
2013-10-29 17:58 ` [RFC/PATCH 1/2] mmc: sdhci: add quirk for broken HS200 support David Cohen
2013-10-29 17:58 ` [RFC/PATCH 2/2] mmc: sdhci-pci: add broken HS200 quirk for Intel Merrifield David Cohen
2013-11-12 21:49 ` [RFC/PATCH 0/2] mmc: sdhci: Workaround Intel Merrifield issue for HS200 David Cohen
2013-12-20 3:00 ` Dong Aisheng
2013-12-20 3:25 ` David Cohen
2013-12-20 3:32 ` Dong Aisheng
2014-01-13 17:55 ` 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=86bnzfdawq.fsf@void.printf.net \
--to=chris@printf.net \
--cc=adrian.hunter@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=dongas86@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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