linux-kernel - Re: [PATCH] time: jiffies.c: fix typos in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 24 Oct 2010 20:08:45 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Kyle Moffett <kyle@...fetthome.net>
cc:	Serafeim Zanikolas <sez@...ian.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] time: jiffies.c: fix typos in comment

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/