From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@paralogos.com>
Cc: David Daney <ddaney@caviumnetworks.com>,
linux-mips@linux-mips.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] MIPS: Don't overflow cevt-r4k.c calculations at high clock rates.
Date: Tue, 18 May 2010 23:52:16 +0100 [thread overview]
Message-ID: <20100518225216.GA18701@linux-mips.org> (raw)
In-Reply-To: <4BF31931.5040704@paralogos.com>
On Tue, May 18, 2010 at 03:48:17PM -0700, Kevin D. Kissell wrote:
> Easy for me to say, of course, but once this patch is accepted, the
> same thing needs to be done to smtc_clockevent_init() in
> cevt-smtc.c.
Thanks for the reminder, Kevin. I'll take care of it.
That said, testing might be a bit harder - there is not enough liquid
helium on the world to get my CoreFPGA3 to run at > 1GHz.
Ralf
next prev parent reply other threads:[~2010-05-18 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 22:11 [PATCH] MIPS: Don't overflow cevt-r4k.c calculations at high clock rates David Daney
2010-05-18 22:48 ` Kevin D. Kissell
2010-05-18 22:52 ` Ralf Baechle [this message]
2010-05-19 1:27 ` Wu Zhangjin
2010-05-19 9:52 ` Sergei Shtylyov
2010-05-19 10:23 ` Thomas Gleixner
2010-05-19 10:34 ` Thomas Gleixner
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=20100518225216.GA18701@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=tglx@linutronix.de \
/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