From: Mukesh Ojha <mojha@codeaurora.org>
To: john.stultz@linaro.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Cc: Mukesh Ojha <mojha@codeaurora.org>
Subject: [PATCH 1/3] time/jiffies: Fixes some typo
Date: Tue, 15 Oct 2019 13:00:03 +0530 [thread overview]
Message-ID: <1571124603-9334-1-git-send-email-mojha@codeaurora.org> (raw)
accuratly => accurately
while at it change `clock source` to clocksource to make
it align with its usage at other places.
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
---
kernel/time/jiffies.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/time/jiffies.c b/kernel/time/jiffies.c
index d23b434..e7f08f2 100644
--- a/kernel/time/jiffies.c
+++ b/kernel/time/jiffies.c
@@ -39,12 +39,12 @@ static u64 jiffies_read(struct clocksource *cs)
/*
* The Jiffies based clocksource is the lowest common
- * denominator clock source which should function on
+ * denominator clocksource which should function on
* all systems. It has the same coarse resolution as
* the timer interrupt frequency HZ and it suffers
* inaccuracies caused by missed or lost timer
* interrupts and the inability for the timer
- * interrupt hardware to accuratly tick at the
+ * interrupt hardware to accurately tick at the
* requested HZ value. It is also not recommended
* for "tick-less" systems.
*/
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
next reply other threads:[~2019-10-15 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 7:30 Mukesh Ojha [this message]
2019-12-10 9:12 ` Mukesh Ojha
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=1571124603-9334-1-git-send-email-mojha@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome