linux-kernel - Re: [PATCH] Documentation/timers/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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.2.00.1006010852470.3637@i5.linux-foundation.org>
Date:	Tue, 1 Jun 2010 08:55:19 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel@...r.kernel.org,
	"arjan@...radead.org" <arjan@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] Documentation/timers/hpet_example.c: only build on X64



On Mon, 31 May 2010, Randy Dunlap wrote:
> 
> We should only build hpet_example on X64, where it is
> implemented.  It can cause build errors on other arch-es.

Both the subject and the body say "X64" (don't use that, btw, it's x86-64, 
please), but the patch itself says CONFIG_X86.

So what is it? Is it any x86, is it just 64-bit, or what? 

So if it's any x86, then please say so in the explanation. And if it's 
really just x86-64, then use CONFIG_X86_64 as the config variable (and 
x86-64 rather than X64 in the commentary).

			Linus
--
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/