From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: remove imxmmc driver
Date: Wed, 11 Apr 2012 22:25:43 +0200 [thread overview]
Message-ID: <20120411202543.GQ3852@pengutronix.de> (raw)
In-Reply-To: <87hawqrq3k.fsf@laptop.org>
On Wed, Apr 11, 2012 at 04:05:51PM -0400, Chris Ball wrote:
> Hi Sascha,
>
> 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>
> > ---
> > drivers/mmc/host/Kconfig | 10 -
> > drivers/mmc/host/Makefile | 1 -
> > drivers/mmc/host/imxmmc.c | 1169 ---------------------------------------------
> > 3 files changed, 1180 deletions(-)
> > delete mode 100644 drivers/mmc/host/imxmmc.c
>
> Looks good, but you missed drivers/mmc/host/imxmmc.h.
Damned, there was a time when drivers had its own header files ;)
Just resent.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-04-11 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 19:55 [PATCH] mmc: remove imxmmc driver Sascha Hauer
2012-04-11 20:05 ` Chris Ball
2012-04-11 20:25 ` Sascha Hauer [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=20120411202543.GQ3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).