From: Steven Cole <elenstev@mesatop.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.61 more accurate spelling of accuracy
Date: 15 Feb 2003 19:23:24 -0700 [thread overview]
Message-ID: <1045362206.5965.58.camel@localhost.localdomain> (raw)
This provides a accurate spelling of accuracy.
Steven
diff -ur linux-2.5.61-1.1027-orig/include/asm-arm/arch-pxa/time.h linux-2.5.61-1.1027/include/asm-arm/arch-pxa/time.h
--- linux-2.5.61-1.1027-orig/include/asm-arm/arch-pxa/time.h Thu Jan 16 19:22:07 2003
+++ linux-2.5.61-1.1027/include/asm-arm/arch-pxa/time.h Sat Feb 15 19:12:18 2003
@@ -53,7 +53,7 @@
int next_match;
/* Loop until we get ahead of the free running timer.
- * This ensures an exact clock tick count and time acuracy.
+ * This ensures an exact clock tick count and time accuracy.
* IRQs are disabled inside the loop to ensure coherence between
* lost_ticks (updated in do_timer()) and the match reg value, so we
* can use do_gettimeofday() from interrupt handlers.
diff -ur linux-2.5.61-1.1027-orig/include/asm-arm/arch-sa1100/time.h linux-2.5.61-1.1027/include/asm-arm/arch-sa1100/time.h
--- linux-2.5.61-1.1027-orig/include/asm-arm/arch-sa1100/time.h Thu Jan 16 19:23:00 2003
+++ linux-2.5.61-1.1027/include/asm-arm/arch-sa1100/time.h Sat Feb 15 19:11:56 2003
@@ -67,7 +67,7 @@
* We will be entered with IRQs enabled.
*
* Loop until we get ahead of the free running timer.
- * This ensures an exact clock tick count and time acuracy.
+ * This ensures an exact clock tick count and time accuracy.
* IRQs are disabled inside the loop to ensure coherence between
* lost_ticks (updated in do_timer()) and the match reg value, so we
* can use do_gettimeofday() from interrupt handlers.
reply other threads:[~2003-02-16 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1045362206.5965.58.camel@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®