linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Jaehoon Chung" <jh80.chung@samsung.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	linux-samsung-soc@vger.kernel.org, "Chris Ball" <cjb@laptop.org>,
	"Kyungmin Park" <kyungmin.park@samsung.com>,
	"kgene kim" <kgene.kim@samsung.com>
Subject: Re: [PATCH v3 0/4] mmc: sdhci-s3c: use the sdhci-pltfm.c and move the header file
Date: Fri, 09 Mar 2012 10:53:26 +0900	[thread overview]
Message-ID: <4F596296.60103@samsung.com> (raw)
In-Reply-To: <20120308110105.GD3638@opensource.wolfsonmicro.com>

On 03/08/2012 08:01 PM, Mark Brown wrote:

> On Thu, Mar 08, 2012 at 02:35:53PM +0900, Jaehoon Chung wrote:
> 
>> So i think no problem that removed "#include <plat/regs-sdhci.h>". is it wrong?
>> Just touching the setup-gpio- files is problem?
> 
> It should be fine, like I say I didn't really read the patches in enough
> detail as the diffstat set off alarm bells.


If you have any opinions, let me know.
I believe that these patches can be maintain more efficiently for eMMC

Best Regards,
Jaehoon Chung
 

  reply	other threads:[~2012-03-09  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  6:17 [PATCH v3 0/4] mmc: sdhci-s3c: use the sdhci-pltfm.c and move the header file Jaehoon Chung
2012-03-06 13:00 ` Mark Brown
2012-03-06 13:15   ` Heiko Stübner
2012-03-06 14:40     ` Jae hoon Chung
2012-03-06 16:30       ` Mark Brown
2012-03-07  3:03         ` Jaehoon Chung
2012-03-07 18:48           ` Mark Brown
2012-03-08  5:35             ` Jaehoon Chung
2012-03-08 11:01               ` Mark Brown
2012-03-09  1:53                 ` Jaehoon Chung [this message]
2012-03-09 11:48                   ` Mark Brown

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=4F596296.60103@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cjb@laptop.org \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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).