linux-kernel - def

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

Message-Id: <48971232.76E4.0078.0@novell.com>
Date:	Mon, 04 Aug 2008 13:29:06 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<mingo@...e.hu>, "Harvey Harrison" <harvey.harrison@...il.com>,
	<tglx@...utronix.de>, "Roman Zippel" <zippel@...ux-m68k.org>,
	"Nick Piggin" <npiggin@...e.de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: def_bool n

Could either of you clarify what the significance of such a construct
(encountered several times in arch/x86/Kconfig alone) is?

At first, I noticed it only with GENERIC_LOCKBREAK (it is my
understanding that this block can go away entirely), but then realized
that with the bool->def_bool conversion this was introduced in various
other places (where "default n" was used before, which seems as
pointless a statement). Am I missing something?

Thanks, Jan

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