public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: zhangfei gao <zhangfei.gao@gmail.com>
Cc: Philip Rakity <prakity@marvell.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Wolfram Sang <w.sang@pengutronix.de>, Chris Ball <cjb@laptop.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Jun Nie <njun@marvell.com>, Raymond Wu <xywu@marvell.com>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Shawn Guo <shawn.guo@linaro.org>, Qiming Wu <wuqm@marvell.com>,
	Eric Miao <eric.y.miao@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/3] provide sdhci driver for mmp2 and pxa910
Date: Tue, 7 Jun 2011 09:00:27 +0200	[thread overview]
Message-ID: <201106070900.27637.arnd@arndb.de> (raw)
In-Reply-To: <BANLkTimkk3JfuVmhuBAw4Op93oDtjKdoXw@mail.gmail.com>

On Tuesday 07 June 2011 07:44:42 zhangfei gao wrote:
> On Sat, Jun 4, 2011 at 5:08 AM, Philip Rakity <prakity@marvell.com> wrote:
> >
> > Please update mmp2 and pxa defconfigs.
> 
> The trend is replacing defconfig with device tree, it may not
> acceptable to update defconfig.

Actually, the defconfigs are not going away, at least not directly.

The device tree will replace the need for individual board files,
but not for defconfig files. As a side-effect, the number of
defconfig files can get reduced, but we should still maintain
them.

	Arnd

      reply	other threads:[~2011-06-07  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  9:48 [PATCH v3 0/3] provide sdhci driver for mmp2 and pxa910 zhangfei gao
2011-06-03 16:20 ` Arnd Bergmann
2011-06-07  5:26   ` zhangfei gao
2011-06-03 21:08 ` Philip Rakity
2011-06-07  5:44   ` zhangfei gao
2011-06-07  7:00     ` Arnd Bergmann [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=201106070900.27637.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=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=nico@fluxnic.net \
    --cc=njun@marvell.com \
    --cc=prakity@marvell.com \
    --cc=shawn.guo@linaro.org \
    --cc=w.sang@pengutronix.de \
    --cc=wuqm@marvell.com \
    --cc=xywu@marvell.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox