public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: [MMC] Fix SD timeout calculation
Date: Thu, 07 Sep 2006 16:51:18 +0200	[thread overview]
Message-ID: <450031E6.7010603@drzeus.cx> (raw)
In-Reply-To: <20060907125840.GA6015@dyn-67.arm.linux.org.uk>

Russell King wrote:
> On Sun, Jun 18, 2006 at 02:34:37PM +0200, Pierre Ossman wrote:
>> Secure Digital cards use a different algorithm to calculate the timeout
>> for data transfers. Using the MMC one works often, but not always.
> 
> Applied, thanks.
> 
> I'm wondering about this cleanup though - both the timeout calculations
> appear to be identical, so making this a library function seems to be
> the right way to go... unless you know different?
> 

Shouldn't be a problem.

Acked-by: Pierre Ossman <drzeus@drzeus.cx>


      reply	other threads:[~2006-09-07 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 12:34 [PATCH] [MMC] Fix SD timeout calculation Pierre Ossman
2006-06-18 12:42 ` Pierre Ossman
2006-09-07 12:58 ` Russell King
2006-09-07 14:51   ` Pierre Ossman [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=450031E6.7010603@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=linux-kernel@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