mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: Serafeim Zanikolas <sez@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] time: jiffies.c: fix typos in comment
Date: Sun, 24 Oct 2010 20:08:45 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1010242006460.13092@localhost6.localdomain6> (raw)
In-Reply-To: <AANLkTin2-h3+ts2JuZ4rxLSppr3Lqh1VCoi3sRQEHoaB@mail.gmail.com>

On Sun, 24 Oct 2010, Kyle Moffett wrote:
> Thomas,
> 
> Please reread the patch again, I think it does exactly what he said it
> did.  Specifically, the old text is:
> >>   * 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
> >>   * for "tick-less" systems.
> 
> While the new text is:
> >>   * 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 accurately tick at the
> >>   * requested HZ value. It is also not recommended
> >>   * for "tick-less" systems.
> 
> I misread it the first time myself, mentally combining the second line
> of the old text with the new text; what you probably saw was:
> 
> >> - * requested HZ value. It is also not reccomended
> >> + * interrupt hardware to accurately tick at the
> >> + * requested HZ value.

Crap yes. I read it twice and still failed to parse it correctly.

Thanks,

	tglx

      reply	other threads:[~2010-10-24 18:09 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
2010-10-24 17:01   ` Kyle Moffett
2010-10-24 18:08     ` Thomas Gleixner [this message]

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.1010242006460.13092@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=kyle@moffetthome.net \
    --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®