linux-kernel - RE: [X86] Fix up silly i1586 boot message.

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:	Thu, 29 Oct 2009 09:33:55 -0700
From:	Yuhong Bao <yuhongbao_386@...mail.com>
To:	<davej@...hat.com>
CC:	<jengelh@...ozas.de>, <macro@...ux-mips.org>,
	<linux-kernel@...r.kernel.org>, <mingo@...e.hu>,
	<tglx@...utronix.de>, <hpa@...or.com>
Subject: RE: [X86] Fix up silly i1586 boot message.


 <20091028154650.GA13660@...hat.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0



>> So that tells us that either NT4 works=2C or nobody uses
>> NT4 on fam15s.
>
> Or that no-one cares.
NT 4 do work on fam15s=2C because 15 truncated to 3 bits is 7=2C while 8 tr=
uncated to 3 bits is 0.
> I don't know why this year and half old thread was resurrected=2C
> but can we all do our bit for lkml traffic reduction and let it die?
> (or at least drop me from the cc. The bug was fixed May 2008=2C
> there's no reason afaics for endless bibble filling everyones inbox).
=A0I know that this bug is now fixed=2C but=A0I wanted to provide more deta=
il on the history behind this.
Yuhong Bao 		 	   		 =20
_________________________________________________________________
Windows 7: Simplify your PC. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=3DPID24727::T:=
WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen1:102009=
--
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/