From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 0/5] make sdhci device drivers self registered
Date: Mon, 21 Mar 2011 01:07:20 -0600 [thread overview]
Message-ID: <AANLkTikmTBTPkAO9uHXtPDqEEheGJitwRKG1RFVDWrCx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimrJ3=GS-+o1vcBpMXg0Phwnu9SVgm0WA-Ck_sf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Mar 21, 2011 at 12:58 AM, Grant Likely
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> On Sun, Mar 20, 2011 at 9:42 PM, Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
>> This patch set is to take sdhci device driver specific things out
>> from sdhci-pltfm.c and make them self registered. Here are the
>> difference it makes.
>>
>> * Get the sdhci device driver follow the Linux trend that driver
>> take the registration by its own
>> * sdhci-pltfm.c becomes significantly simpler and only has common
>> support functions there
>> * All sdhci device specific stuff are going back its own driver
>> * The dt and non-dt support share the same pair of .probe and
>> .remove hooks.
>
> Fantastic! Thanks for taking this on. I'll make a few comments, but
> this series really needs to be reposted to both the linux-kernel and
> linux-mmc lists.
>
On a brief glance, it looks pretty good. I need to take a deeper read
into it tomorrow, but in general I like the way this series is
looking. If you do the reposting right away, then I can make my
comments on the linux-mmc list.
Also, don't forget to cc: samuel when you repost.
g.
next prev parent reply other threads:[~2011-03-21 7:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 3:42 [PATCH 0/5] make sdhci device drivers self registered Shawn Guo
[not found] ` <1300678938-8046-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-03-21 3:42 ` [PATCH 1/5] mmc: sdhci: make sdhci-esdhc-imx driver " Shawn Guo
2011-03-21 3:42 ` [PATCH 2/5] mmc: sdhci: make sdhci-cns3xxx " Shawn Guo
2011-03-21 3:42 ` [PATCH 3/5] mmc: sdhci: make sdhci-dove " Shawn Guo
2011-03-21 3:42 ` [PATCH 4/5] mmc: sdhci: make sdhci-tegra " Shawn Guo
2011-03-21 3:42 ` [PATCH 5/5] mmc: sdhci: update Makefile/Kconfig for sdhci_pltfm change Shawn Guo
2011-03-21 6:58 ` [PATCH 0/5] make sdhci device drivers self registered Grant Likely
[not found] ` <AANLkTimrJ3=GS-+o1vcBpMXg0Phwnu9SVgm0WA-Ck_sf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-21 7:07 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-21 8:06 Shawn Guo
[not found] ` <1300694823-8300-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-03-21 12:39 ` Arnd Bergmann
[not found] ` <201103211339.45305.arnd-r2nGTMty4D4@public.gmane.org>
2011-03-21 12:52 ` Shawn Guo
2011-03-21 12:54 ` Wolfram Sang
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=AANLkTikmTBTPkAO9uHXtPDqEEheGJitwRKG1RFVDWrCx@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).