All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stefan Nilsson XK <stefan.xk.nilsson@stericsson.com>,
	linux-mmc@vger.kernel.org, Per Forlin <per.forlin@stericsson.com>,
	Ulf Hansson <ulf.hansson@stericsson.com>
Subject: Re: [PATCH] mmc: core: Quirk for long data read time
Date: Fri, 11 Nov 2011 21:37:18 -0500	[thread overview]
Message-ID: <87sjluhxr5.fsf@laptop.org> (raw)
In-Reply-To: <CAKnu2Mqr2Vi8f3KkgmQxywucAS9BN4rY-SxSOiFd5oV06sZ12w@mail.gmail.com> (Linus Walleij's message of "Thu, 3 Nov 2011 12:32:06 +0100")

Hi,

On Thu, Nov 03 2011, Linus Walleij wrote:
> 2011/11/3 Stefan Nilsson XK <stefan.xk.nilsson@stericsson.com>:
>
>> Adds a quirk that sets the data read timeout to a fixed value instead
>> of relying on the information in the CSD. The timeout value choosen
>> is 300ms since that has proven enough for the problematic cards found,
>> but could be increased if other cards require this.
>>
>> This patch also enables this quirk for certain Micron cards known to
>> have this problem.
>>
>> Signed-off-by: Stefan Nilsson XK <stefan.xk.nilsson@stericsson.com>
>> Signed-off-by: Ulf Hansson <ulf.hansson@stericsson.com>
>
> And I thought it was enough with *people* who didn't deliver stuff
> they promised in due time, now even *memory cards* miss their
> own promised deadlines.... :-)
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> This should go into stable as well right?

Thanks, pushed to mmc-next for 3.2 with Linus W's ACK and a stable@ tag.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-11-12  2:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  8:44 [PATCH] mmc: core: Quirk for long data read time Stefan Nilsson XK
2011-11-03 11:32 ` Linus Walleij
2011-11-12  2:37   ` Chris Ball [this message]
2011-11-12  2:40 ` Chris Ball
2011-11-14  9:05   ` Ulf Hansson

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=87sjluhxr5.fsf@laptop.org \
    --to=cjb@laptop.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=stefan.xk.nilsson@stericsson.com \
    --cc=ulf.hansson@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.