public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linux-mmc@vger.kernel.org, Seungwon Jeon <tgih.jun@samsung.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v4 0/3] mmc: dw_mmc: Add support for Rockchip variant
Date: Thu, 27 Jun 2013 11:56:06 -0400	[thread overview]
Message-ID: <87ppv7mtt5.fsf@octavius.laptop.org> (raw)
In-Reply-To: <201306131055.49595.heiko@sntech.de> ("Heiko \=\?utf-8\?Q\?St\?\= \=\?utf-8\?Q\?\=C3\=BCbner\=22's\?\= message of "Thu, 13 Jun 2013 10:55:48 +0200")

Hi Heiko,

On Thu, Jun 13 2013, Heiko Stübner wrote:
> The driver support for the mmc host is not needed for the core SoC support
> and in the same way the mmc support does not need the SoC code to function.
> Therefore it can be submitted (and hopefully merged) on its own.
>
>
> Changes since v3:
> - submit mmc driver standalone
> - add dt binding documentation

Thanks, all three patches pushed to mmc-next for 3.11.

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

      parent reply	other threads:[~2013-06-27 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  8:55 [PATCH v4 0/3] mmc: dw_mmc: Add support for Rockchip variant Heiko Stübner
2013-06-13  8:56 ` [PATCH v4 1/3] mmc: dw_mmc-pltfm: remove static from dw_mci_pltfm_remove Heiko Stübner
2013-06-13  8:57 ` [PATCH v4 2/3] mmc: dw_mmc-pltfm: move probe and remove below dt match table Heiko Stübner
2013-06-13  8:58 ` [PATCH v4 3/3] mmc: dw_mmc-pltfm: add Rockchip variant Heiko Stübner
2013-06-27 15:56 ` 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=87ppv7mtt5.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=heiko@sntech.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tgih.jun@samsung.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