From: Chris Ball <cjb@laptop.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-mmc@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Add SDHCI ACPI driver
Date: Thu, 22 Nov 2012 08:55:45 -0500 [thread overview]
Message-ID: <87k3tdagim.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1353573830-13006-1-git-send-email-adrian.hunter@intel.com> (Adrian Hunter's message of "Thu, 22 Nov 2012 10:43:47 +0200")
Hi,
On Thu, Nov 22 2012, Adrian Hunter wrote:
> Here is SDHCI ACPI driver. It is dependent on new ACPI Platform support
> so I suggest Rafael takes the patches with Chris' Ack.
>
> Please note that I would prefer this to be queued for 3.8
Looks fine:
Acked-by: Chris Ball <cjb@laptop.org>
I have some dumb questions, though -- what kind of platforms ship with
these devices? Do they ever have the controller on PCI too, and what
happens with sdhci-pci vs. sdhci-acpi in that case?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-11-22 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:43 [PATCH 0/3] Add SDHCI ACPI driver Adrian Hunter
2012-11-22 8:43 ` [PATCH 1/3] PNPACPI: exclude SDHCI devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 2/3] ACPI: add SDHCI to ACPI platform devices Adrian Hunter
2012-11-22 8:43 ` [PATCH 3/3] mmc: sdhci-acpi: add SDHCI ACPI driver Adrian Hunter
2012-11-23 9:44 ` Mika Westerberg
2012-11-22 13:55 ` Chris Ball [this message]
2012-11-22 14:46 ` [PATCH 0/3] Add " Adrian Hunter
2012-11-22 21:24 ` Rafael J. Wysocki
2012-11-23 9:34 ` Mika Westerberg
2012-11-23 10:13 ` Adrian Hunter
2012-11-23 10:50 ` Rafael J. Wysocki
2012-11-23 10:23 ` Adrian Hunter
2012-11-23 10:51 ` Rafael J. Wysocki
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=87k3tdagim.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=adrian.hunter@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@sisk.pl \
/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).