From: Chris Ball <cjb@laptop.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH v2] mmc: remove imxmmc driver
Date: Wed, 11 Apr 2012 16:27:44 -0400 [thread overview]
Message-ID: <87d37erp33.fsf@laptop.org> (raw)
In-Reply-To: <1334175889-30118-1-git-send-email-s.hauer@pengutronix.de> (Sascha Hauer's message of "Wed, 11 Apr 2012 22:24:49 +0200")
Hi,
On Wed, Apr 11 2012, Sascha Hauer wrote:
> This driver is broken since 2.6.31 when the traditional i.MX1
> support was removed.
>
> In theory the i.MX1 mmc controller can be supported by the mxcmmc
> driver which basically is the same hardware. However, the i.MX1
> controller has severe bugs which made several workarounds necessary which
> resulted in a different driver structure. At that time it seemed easier
> to write a second driver to support hardware without bugs.
>
> As noone cared for the i.MX1 driver for a long time and it does
> not compile, remove it.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>
> v2: Also remove imxmmc.h
>
> drivers/mmc/host/Kconfig | 10 -
> drivers/mmc/host/Makefile | 1 -
> drivers/mmc/host/imxmmc.c | 1169 ---------------------------------------------
> drivers/mmc/host/imxmmc.h | 64 ---
> 4 files changed, 1244 deletions(-)
> delete mode 100644 drivers/mmc/host/imxmmc.c
> delete mode 100644 drivers/mmc/host/imxmmc.h
Thanks! Pushed to mmc-next for 3.5.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
WARNING: multiple messages have this Message-ID (diff)
From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] mmc: remove imxmmc driver
Date: Wed, 11 Apr 2012 16:27:44 -0400 [thread overview]
Message-ID: <87d37erp33.fsf@laptop.org> (raw)
In-Reply-To: <1334175889-30118-1-git-send-email-s.hauer@pengutronix.de> (Sascha Hauer's message of "Wed, 11 Apr 2012 22:24:49 +0200")
Hi,
On Wed, Apr 11 2012, Sascha Hauer wrote:
> This driver is broken since 2.6.31 when the traditional i.MX1
> support was removed.
>
> In theory the i.MX1 mmc controller can be supported by the mxcmmc
> driver which basically is the same hardware. However, the i.MX1
> controller has severe bugs which made several workarounds necessary which
> resulted in a different driver structure. At that time it seemed easier
> to write a second driver to support hardware without bugs.
>
> As noone cared for the i.MX1 driver for a long time and it does
> not compile, remove it.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>
> v2: Also remove imxmmc.h
>
> drivers/mmc/host/Kconfig | 10 -
> drivers/mmc/host/Makefile | 1 -
> drivers/mmc/host/imxmmc.c | 1169 ---------------------------------------------
> drivers/mmc/host/imxmmc.h | 64 ---
> 4 files changed, 1244 deletions(-)
> delete mode 100644 drivers/mmc/host/imxmmc.c
> delete mode 100644 drivers/mmc/host/imxmmc.h
Thanks! Pushed to mmc-next for 3.5.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-04-11 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 20:24 [PATCH v2] mmc: remove imxmmc driver Sascha Hauer
2012-04-11 20:24 ` Sascha Hauer
2012-04-11 20:27 ` Chris Ball [this message]
2012-04-11 20:27 ` Chris Ball
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=87d37erp33.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.