linux-kernel - Re: [PATCH] wireless: fix regression caused by regulatory config option

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]

Date:	Sun, 26 Oct 2008 13:16:44 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"John W. Linville" <linville@...driver.com>
cc:	Arjan van de Ven <arjan@...radead.org>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, rjw@...k.pl, rodriguez@...eros.com,
	johannes@...solutions.net
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config
 option



On Sun, 26 Oct 2008, John W. Linville wrote:
> 
> Is it common practice to have compatibility options default to
> "y"?  I'm not saying it shouldn't be, just wondering if it has been
> traditionally?

Yes. Generally the rule should be that

	make oldconfig

with 'default values for all new options' should give you a configuration 
that is essentially identical to the old one.

So if it's a config option to enable compatibility with old kernels, it 
should default to 'y'. If it's a new driver or a new feature that didn't 
exist in previous kernels, it should default to 'n'.

			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/