All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: zhangfei gao <zhangfei.gao@gmail.com>
Cc: Matt Fleming <matt@console-pimps.org>,
	eric.y.miao@gmail.com, linux-mmc@vger.kernel.org,
	Wolfram Sang <w.sang@pengutronix.de>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 1/1]MMC: add support of sdhci-pxa driver
Date: Thu, 21 Oct 2010 15:52:49 +0100	[thread overview]
Message-ID: <20101021145249.GA13095@void.printf.net> (raw)
In-Reply-To: <20101021141302.GA11912@void.printf.net>

Hi,

On Thu, Oct 21, 2010 at 03:13:02PM +0100, Chris Ball wrote:
> On Mon, Oct 18, 2010 at 08:32:46AM -0400, zhangfei gao wrote:
> > Update with comments from Matt and Eric.
> > Test with sd and emmc.
> > 
> > >From e5dd554ed4d3488a83d9a4888d68d1d85482f747 Mon Sep 17 00:00:00 2001
> > From: Zhangfei Gao <zhangfei.gao@marvell.com>
> > Date: Mon, 20 Sep 2010 10:51:28 -0400
> > Subject: [PATCH] mmc: add support of sdhci-pxa driver
> > 
> > 	Support Marvell PXA168/PXA910/MMP2 SD Host Controller
> > 
> > Signed-off-by: Zhangfei Gao <zhangfei.gao@marvell.com>
> > ---
> >  arch/arm/plat-pxa/include/plat/sdhci.h |   32 ++++
> >  drivers/mmc/host/Kconfig               |   12 ++
> >  drivers/mmc/host/Makefile              |    1 +
> >  drivers/mmc/host/sdhci-pxa.c           |  259 ++++++++++++++++++++++++++++++++
> >  4 files changed, 304 insertions(+), 0 deletions(-)
> >  create mode 100644 arch/arm/plat-pxa/include/plat/sdhci.h
> >  create mode 100644 drivers/mmc/host/sdhci-pxa.c
> 
> I'll take the drivers/mmc/ hunks, but you should send the plat-pxa/
> patch through the ARM tree.

Oh.  If we do that then the driver won't compile until everything's
together, because it #includes <plat/sdhci.h>.  Haojian/Eric, what do
you prefer here?  Should I take the arch/arm/ hunk via the MMC tree?
(If so, please provide ACKs.)

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/1]MMC: add support of sdhci-pxa driver
Date: Thu, 21 Oct 2010 15:52:49 +0100	[thread overview]
Message-ID: <20101021145249.GA13095@void.printf.net> (raw)
In-Reply-To: <20101021141302.GA11912@void.printf.net>

Hi,

On Thu, Oct 21, 2010 at 03:13:02PM +0100, Chris Ball wrote:
> On Mon, Oct 18, 2010 at 08:32:46AM -0400, zhangfei gao wrote:
> > Update with comments from Matt and Eric.
> > Test with sd and emmc.
> > 
> > >From e5dd554ed4d3488a83d9a4888d68d1d85482f747 Mon Sep 17 00:00:00 2001
> > From: Zhangfei Gao <zhangfei.gao@marvell.com>
> > Date: Mon, 20 Sep 2010 10:51:28 -0400
> > Subject: [PATCH] mmc: add support of sdhci-pxa driver
> > 
> > 	Support Marvell PXA168/PXA910/MMP2 SD Host Controller
> > 
> > Signed-off-by: Zhangfei Gao <zhangfei.gao@marvell.com>
> > ---
> >  arch/arm/plat-pxa/include/plat/sdhci.h |   32 ++++
> >  drivers/mmc/host/Kconfig               |   12 ++
> >  drivers/mmc/host/Makefile              |    1 +
> >  drivers/mmc/host/sdhci-pxa.c           |  259 ++++++++++++++++++++++++++++++++
> >  4 files changed, 304 insertions(+), 0 deletions(-)
> >  create mode 100644 arch/arm/plat-pxa/include/plat/sdhci.h
> >  create mode 100644 drivers/mmc/host/sdhci-pxa.c
> 
> I'll take the drivers/mmc/ hunks, but you should send the plat-pxa/
> patch through the ARM tree.

Oh.  If we do that then the driver won't compile until everything's
together, because it #includes <plat/sdhci.h>.  Haojian/Eric, what do
you prefer here?  Should I take the arch/arm/ hunk via the MMC tree?
(If so, please provide ACKs.)

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  parent reply	other threads:[~2010-10-21 14:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 12:32 [PATCH V3 1/1]MMC: add support of sdhci-pxa driver zhangfei gao
2010-10-18 14:58 ` Wolfram Sang
2010-10-18 15:25   ` zhangfei gao
2010-10-19  2:03     ` Wolfram Sang
2010-10-19  9:44       ` zhangfei gao
2010-10-21 14:13 ` Chris Ball
2010-10-21 14:20   ` zhangfei gao
2010-10-21 14:52   ` Chris Ball [this message]
2010-10-21 14:52     ` Chris Ball
2010-10-22  0:20     ` Marek Vasut
2010-10-22  0:20       ` Marek Vasut
2010-10-22  0:27       ` Chris Ball
2010-10-22  0:27         ` Chris Ball
2010-10-22  8:44     ` Haojian Zhuang
2010-10-22  8:44       ` Haojian Zhuang
2010-10-22  9:58       ` Chris Ball
2010-10-22  9:58         ` Chris Ball
2010-10-22 11:04         ` Chris Ball
2010-10-22 11:04           ` Chris Ball
2010-10-22 14:09           ` zhangfei gao
2010-10-22 14:09             ` zhangfei gao
2010-10-23 14:24             ` Marek Vasut
2010-10-23 14:24               ` Marek Vasut
2010-10-23 16:47               ` zhangfei gao
2010-10-23 16:47                 ` zhangfei gao
2010-10-23 17:50                 ` Marek Vasut
2010-10-23 17:50                   ` Marek Vasut
2010-10-24  3:26                   ` zhangfei gao
2010-10-24  3:26                     ` zhangfei gao
2010-10-24  4:02                     ` Marek Vasut
2010-10-24  4:02                       ` Marek Vasut
2010-10-25  5:48                       ` zhangfei gao
2010-10-25  5:48                         ` zhangfei gao

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=20101021145249.GA13095@void.printf.net \
    --to=cjb@laptop.org \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=w.sang@pengutronix.de \
    --cc=zhangfei.gao@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.