From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: remove linux/blkdev.h include from host drivers
Date: Wed, 11 Apr 2012 18:52:23 +0200 [thread overview]
Message-ID: <20120411165223.GP3852@pengutronix.de> (raw)
In-Reply-To: <87ty0qs2fz.fsf@laptop.org>
On Wed, Apr 11, 2012 at 11:39:12AM -0400, Chris Ball wrote:
> Hi Sascha, Wolfram,
>
> On Tue, Apr 10 2012, Dmitry Artamonow wrote:
> > I've compile tested everything with and without CONFIG_BLOCK enabled,
> > except for imxmmc.c - this driver seems to be long time broken
> > (at least since the removal of mach-imx in 2.6.31 - see commit
> > 1341d34ffc296f98dc84876f35f3151525dc02a2 )
>
> I can confirm that it no longer builds:
>
> /home/cjb/git/mmc/drivers/mmc/host/imxmmc.c:32:26: fatal error: mach/imx-dma.h: No such file or directory
>
> Should imxmmc simply be removed from drivers/mmc/host? Do any of the
> more current i.MX MMC drivers support the same hardware?
It has long been on my todo list to remove this driver. The more recent
i.MX use the mxcmmc driver which is basically the same hardware but
without a bunch of bugs which made the older imxmmc driver unusable on
newer hardware. I can send a patch if you like.
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 |
next prev parent reply other threads:[~2012-04-11 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 19:06 [PATCH] mmc: remove linux/blkdev.h include from host drivers Dmitry Artamonow
2012-04-11 10:11 ` Will Newton
2012-04-11 15:05 ` Ludovic Desroches
2012-04-11 15:39 ` Chris Ball
2012-04-11 16:52 ` Sascha Hauer [this message]
2012-04-11 16:58 ` 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=20120411165223.GP3852@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).