From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS: Outline udelay and fix a few issues.
Date: Tue, 9 Jun 2009 13:20:17 +0100 [thread overview]
Message-ID: <20090609122017.GA14202@linux-mips.org> (raw)
In-Reply-To: <20090609.111248.161838296.nemoto@toshiba-tops.co.jp>
On Tue, Jun 09, 2009 at 11:12:48AM +0900, Atsushi Nemoto wrote:
> > Relying on pure C for computation of the delay value removes the need for
> > explicit. The price we pay is a slight slowdown of the computation - to
> > be fixed on another day.
>
> Please fix this commit.
Sigh. I wonder how this wrong version made it into my tree. Oh well,
applied. No time to fuzz around before 2.6.30 even though I'd like to
avoid the 64-bit arithmetic.
Applied. Thanks!
Ralf
next prev parent reply other threads:[~2009-06-09 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20022929AbZFHPuy/20090608155054Z+9196@ftp.linux-mips.org>
2009-06-09 2:12 ` MIPS: Outline udelay and fix a few issues Atsushi Nemoto
2009-06-09 12:03 ` Florian Fainelli
2009-06-09 12:20 ` Ralf Baechle [this message]
2009-06-10 12:56 ` Geert Uytterhoeven
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=20090609122017.GA14202@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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