linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: avorontsov@ru.mvista.com
Cc: Liu Dave <DaveLiu@freescale.com>,
	D'Abbraccio Joe-LJD015 <Joe.D'abbraccio@freescale.com>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Xie Xiaobo-R63061 <X.Xie@freescale.com>,
	Lai Kon-LKL001 <Konjin.Lai@freescale.com>
Subject: Re: [PATCH] mmc: Add driver for Freescale eSDHC controllers
Date: Thu, 15 Jan 2009 06:55:02 +0100	[thread overview]
Message-ID: <20090115065502.1b719b06@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20090114235605.GA13531@oksana.dev.rtsoft.ru>

On Thu, 15 Jan 2009 02:56:05 +0300
Anton Vorontsov <avorontsov@ru.mvista.com> wrote:

> 
> Ah. I wonder why Freescale just didn't write some patches for sdhci,
> but copied the code instead...
> 

Probably because it was quicker. Samsung did the same thing, but now
Ben Dooks has patches to properly support it via sdhci.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

  reply	other threads:[~2009-01-15  6:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 19:46 [PATCH] mmc: Add driver for Freescale eSDHC controllers Anton Vorontsov
2009-01-14 23:37 ` Liu Dave
2009-01-14 23:56   ` Anton Vorontsov
2009-01-15  5:55     ` Pierre Ossman [this message]
2009-01-15  6:11       ` Liu Dave
2009-01-15  6:39         ` Pierre Ossman
2009-01-15  6:56           ` Liu Dave
2009-01-15 14:35     ` Ben Dooks
2009-01-15  3:43 ` Kumar Gala
2009-01-22  1:35   ` Anton Vorontsov
2009-01-15 21:52 ` Arnd Bergmann

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=20090115065502.1b719b06@mjolnir.drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=DaveLiu@freescale.com \
    --cc=Joe.D'abbraccio@freescale.com \
    --cc=Konjin.Lai@freescale.com \
    --cc=X.Xie@freescale.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).