From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jae hoon Chung <jh80.chung@gmail.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"Jaehoon Chung" <jh80.chung@samsung.com>,
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: Tue, 6 Mar 2012 16:30:52 +0000 [thread overview]
Message-ID: <20120306163052.GX19635@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAELcNGS6UynrJPRk1KtEJT3Rm6Jb5_scLm4KKca+dJ1ZYDOVbg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Tue, Mar 06, 2012 at 11:40:08PM +0900, Jae hoon Chung wrote:
> 2012/3/6 Heiko Stübner <heiko@sntech.de>:
> > Am Dienstag, 6. März 2012, 14:00:54 schrieb Mark Brown:
> >> This series will break S3C64xx, you've not touched it at all in the
> >> update but it uses the same SDHCI controller.
> > This problem will probably also surface for the S3C2416 which also uses the
> > same SDHCI controller.
> i didn't know why will break on them. Could you explain to me?
> Are there codes which affect S3C64XX and S3C24XX?
> If i miss out something, let me know.
The same IP is present and used with the same driver on other Samsung
SoCs.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-06 16:30 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 [this message]
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
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=20120306163052.GX19635@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=heiko@sntech.de \
--cc=jh80.chung@gmail.com \
--cc=jh80.chung@samsung.com \
--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).