linux-kernel - Re: [PATCH] Blacklist Dell Optiplex 320 from using the HPET

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]

Message-ID: <20070507204118.GB9822@khazad-dum.debian.net>
Date:	Mon, 7 May 2007 17:41:18 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Andreas Mohr <andi@...x01.hs-esslingen.de>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Guilherme M. Schroeder" <guilherme@...tralinf.com.br>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Blacklist Dell Optiplex 320 from using the HPET

On Mon, 07 May 2007, Andreas Mohr wrote:
> On Sat, May 05, 2007 at 12:58:15PM -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 05 May 2007, Thomas Gleixner wrote:
> > > +		printk(KERN_WARNING "HPET counter is defect\n");
> > 
> > What about
> > 		printk(KERN_WARNING "HPET counter is stopped\n");
> > 
> > which is far more descriptive?
> 
> Far more misguiding, rather?

True, one can miss the "is".

> "HPET counter inoperable or defective (no increment found during probing)"?
> (with an optional "please report" part)

Yes, this looks better.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
-
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/