From: Chris Ball <cjb@laptop.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Dmitry Artamonow <mad_soft@inbox.ru>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH] mmc: remove linux/blkdev.h include from host drivers
Date: Wed, 11 Apr 2012 12:58:58 -0400 [thread overview]
Message-ID: <87pqberyr1.fsf@laptop.org> (raw)
In-Reply-To: <20120411165223.GP3852@pengutronix.de> (Sascha Hauer's message of "Wed, 11 Apr 2012 18:52:23 +0200")
Hi,
On Wed, Apr 11 2012, Sascha Hauer wrote:
>> 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.
Thanks, let's do it.
It would be nice to have a story for how MX1 users can use their
hardware with modern kernels, even if it's just "It should be possible
to modify the mxcmmc driver to support this older hardware, and the sort
of changes that need to be made are <..>".
(Dmitry, your patch is fine -- I can remove the imxmmc hunk from it when
applying.)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-04-11 16:58 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
2012-04-11 16:58 ` Chris Ball [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=87pqberyr1.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mad_soft@inbox.ru \
--cc=s.hauer@pengutronix.de \
--cc=w.sang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox