linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, Anton Vorontsov <cbouatmailru@gmail.com>
Subject: Re: [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook.
Date: Sat, 12 Feb 2011 21:43:50 +0100	[thread overview]
Message-ID: <20110212204350.GA23657@pengutronix.de> (raw)
In-Reply-To: <20110212202212.GA11375@void.printf.net>

On Sat, Feb 12, 2011 at 08:22:12PM +0000, Chris Ball wrote:
> Hi Wolfram,
> 
> On Mon, Feb 07, 2011 at 06:48:39PM +0100, Wolfram Sang wrote:
> > Hmm, for now I don't have a better alternative, but I somehow hink there must
> > be a better solution than to add one hook per [...]
> 
> If there still isn't a better alternative in mind, I'm thinking about
> going ahead and taking this patch, and then reusing the quirk bit for
> Chuanxiao's "mmc: set a suitable max_discard_sectors value for HC"
> patchset.

What about using the SZ_2048 quirk instead which could be done via
io-accessors? That being said, I have a train travel tomorrow and will try to
see if a fixup() function would make sense for this one. Can you wait one more
day?

Thanks,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2011-02-12 20:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  6:13 [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook Chris Ball
2011-02-07 17:48 ` Wolfram Sang
2011-02-12 20:22   ` Chris Ball
2011-02-12 20:43     ` Wolfram Sang [this message]
2011-02-12 21:05       ` Chris Ball
2011-02-13 21:13         ` Wolfram Sang
2011-05-29  2:28 ` 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=20110212204350.GA23657@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.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).