linux-kernel - Re: [PATCH 2/4] x86_64 boot -v2: Add linked list of struct setup

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <47F3B6B6.9010802@zytor.com>
Date:	Wed, 02 Apr 2008 09:39:18 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Paul Jackson <pj@....com>
CC:	"Huang, Ying" <ying.huang@...el.com>, andi@...stfloor.org,
	mingo@...hat.com, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] x86_64 boot -v2: Add linked list of struct setup_data

Paul Jackson wrote:
> Huang wrote:
>> On Sat, 2008-03-29 at 23:31 -0500, Paul Jackson wrote:
>>> Huang wrote:
>>>> +/* setup data types */
>>>> +#define SETUP_NONE			0
>>> This define seems unused?
>> I think this can prevent somebody to use 0 as type id.
> 
> Why is it a good idea to prevent a 0 type id?
> 

It is usually handy to have an ID to use as ignore, or not present, and 
for that to be zero.

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