From: Juan Quintela <quintela@mandrakesoft.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] loosing time with CPU counter timer
Date: Tue, 15 Apr 2003 02:54:19 +0200 [thread overview]
Message-ID: <86ades8ts4.fsf@trasno.mitica> (raw)
In-Reply-To: <20030414171655.G1642@mvista.com> (Jun Sun's message of "Mon, 14 Apr 2003 17:16:55 -0700")
>>>>> "jun" == Jun Sun <jsun@mvista.com> writes:
Hi
only aesthetical fixes:
jun> diff -Nru linux/arch/mips/ddb5xxx/ddb5477/setup.c.orig linux/arch/mips/ddb5xxx/ddb5477/setup.c
jun> --- linux/arch/mips/ddb5xxx/ddb5477/setup.c.orig Mon Apr 14 15:28:57 2003
jun> +++ linux/arch/mips/ddb5xxx/ddb5477/setup.c Mon Apr 14 16:08:35 2003
jun> @@ -330,6 +348,16 @@
jun> * high-level timer interrupt service routines. This function
jun> * is set as irqaction->handler and is invoked through do_IRQ.
jun> */
jun> +static inline int
jun> +64bit_compare(unsigned hi1, unsigned lo1, unsigned hi2, unsigned lo2)
Please, use "unsigned int" /me notices that file is not consistent, in
some places it uses "unsigned" and in other "unsigned int".
jun> +{
jun> + if (hi1 == hi2) {
jun> + return lo1 - lo2;
jun> + } else {
jun> + return hi1 - hi2;
jun> + }
jun> +}
Ralf tax on braces apply here.
jun> + /* check to see if we have missed a timer interrupt */
jun> + if (64bit_compare(timerhi, timerlo, expirehi, expirelo) < 0) {
jun> + unsigned int old_expirelo=expirelo;
jun> + expirelo += cycles_per_jiffy;
jun> + expirehi += (expirelo < old_expirelo);
Tax on parens :)
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-04-15 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 0:16 [PATCH] loosing time with CPU counter timer Jun Sun
2003-04-15 0:54 ` Juan Quintela [this message]
2003-04-21 21:22 ` Jun Sun
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=86ades8ts4.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=jsun@mvista.com \
--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 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.