All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Haijun Zhang <Haijun.Zhang@freescale.com>
Cc: linux-mmc@vger.kernel.org, Jerry Huang <Chang-Ming.Huang@freescale.com>
Subject: Re: [PATCH] Powerpc eSDHC: Use u64 to calculate the timeout value to avoid overflow
Date: Sun, 25 Nov 2012 14:49:30 -0500	[thread overview]
Message-ID: <87mwy58nud.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1353303061-16679-2-git-send-email-Haijun.Zhang@freescale.com> (Haijun Zhang's message of "Mon, 19 Nov 2012 13:31:00 +0800")

Hi,

On Mon, Nov 19 2012, Haijun Zhang wrote:
> As some mmc cards need large timeout value usually a few seconds,
> so data timeout nanosecond will overflow with u32 variable and
> give the wrong timeout value, so use u64 will be safe.
>
> Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
> Signed-off-by: Haijun Zhang <Haijun.Zhang@freescale.com>
> Acked-by: Anton Vorontsov <cbouatmailru@gmail.com>

Thanks, pushed to mmc-next for 3.8.

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

  reply	other threads:[~2012-11-25 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  5:30 [PATCH 2/2 v3] Powerpc/eSDHC: Add limit to data and erase timeout value calculation Haijun Zhang
2012-11-19  5:31 ` [PATCH] Powerpc eSDHC: Use u64 to calculate the timeout value to avoid overflow Haijun Zhang
2012-11-25 19:49   ` Chris Ball [this message]
2012-11-19  5:31 ` [PATCH 1/2 v3] Powerpc/eSDHC: Calculate the applicable mmc erase timeout value Haijun Zhang
2012-11-25 19:54   ` Chris Ball
  -- strict thread matches above, loose matches on Subject: below --
2012-11-19  3:38 [PATCH] Powerpc eSDHC: Use u64 to calculate the timeout value to avoid overflow Haijun Zhang
2012-11-19  5:02 ` Anton Vorontsov
2012-11-12  4:45 Haijun Zhang
2012-11-19  0:39 ` Anton Vorontsov

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=87mwy58nud.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=Chang-Ming.Huang@freescale.com \
    --cc=Haijun.Zhang@freescale.com \
    --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 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.