mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Serafeim Zanikolas <sez@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] time: jiffies.c: fix typos in comment
Date: Sun, 24 Oct 2010 16:22:57 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1010241618480.8736@localhost6.localdomain6> (raw)
In-Reply-To: <1287849986-5936-1-git-send-email-sez@debian.org>



On Sat, 23 Oct 2010, Serafeim Zanikolas wrote:

> 
> Signed-off-by: Serafeim Zanikolas <sez@debian.org>
> ---
>  kernel/time/jiffies.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/time/jiffies.c b/kernel/time/jiffies.c
> index 5404a84..12ba9a7 100644
> --- a/kernel/time/jiffies.c
> +++ b/kernel/time/jiffies.c
> @@ -30,8 +30,8 @@
>   * 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
> - * requested HZ value. It is also not reccomended
> + * interrupt hardware to accurately tick at the
> + * requested HZ value. It is also not recommended
>   * for "tick-less" systems.

You are not only correcting a typo. You are changing the sense of the
comment, unfortunately in the wrong way.

Why wouldn't it be recommended that the interrupt hardware ticks at
the requested HZ value ? 

The inability of it to tick accurately at the requested HZ value is
one of the causes which make jiffies clocksource inaccurate. And that
what the comment says.

Thanks,

	tglx

  reply	other threads:[~2010-10-24 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 16:06 Serafeim Zanikolas
2010-10-24 14:22 ` Thomas Gleixner [this message]
2010-10-24 17:01   ` Kyle Moffett
2010-10-24 18:08     ` 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=alpine.LFD.2.00.1010241618480.8736@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sez@debian.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

all inboxes | Powered by JetHome®