From: Wolfram Sang <w.sang@pengutronix.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Philip Rakity <prakity@marvell.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Zhangfei Gao <zhangfei.gao@gmail.com>
Subject: Re: can we remove the quirk SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN ?
Date: Tue, 9 Nov 2010 13:27:29 +0100 [thread overview]
Message-ID: <20101109122729.GG3223@pengutronix.de> (raw)
In-Reply-To: <20101109120835.0fea3feb@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Tue, Nov 09, 2010 at 12:08:35PM +0000, Alan Cox wrote:
> I think I agree with Wolfram. Perhaps a much better model would be
>
> "Anyone who adds a quirk will have to figure out how to remove one"
>
> Several are trivial to remove and generalise into a couple of function
> overrides.
My favourite would be one concentrated action to remove a couple of
those quirks while adding well defined hooks to reduce the need of new
ones. I have a few ideas and am currently trying a few options to get it
funded :)
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-09 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D68A6A7-2D95-463F-875B-DB52ECCC53F1@marvell.com>
2010-11-09 11:45 ` Fwd: can we remove the quirk SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN ? Philip Rakity
2010-11-09 11:55 ` Wolfram Sang
2010-11-09 12:02 ` Philip Rakity
2010-11-09 12:08 ` Alan Cox
2010-11-09 12:27 ` Wolfram Sang [this message]
2010-11-09 12:21 ` Wolfram Sang
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=20101109122729.GG3223@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
--cc=zhangfei.gao@gmail.com \
/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