LKML Archive on
help / color / mirror / Atom feed
From: Linus Torvalds <>
To: "John W. Linville" <>
Cc: Arjan van de Ven <>,,,,,
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config option
Date: Sun, 26 Oct 2008 13:16:44 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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'.


  reply	other threads:[~2008-10-26 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 17:30 Arjan van de Ven
2008-10-26 20:09 ` John W. Linville
2008-10-26 20:16   ` Linus Torvalds [this message]
2008-10-26 20:18   ` Arjan van de Ven
2008-10-26 20:22     ` Johannes Berg
2008-10-27 20:42       ` Pavel Machek
2008-10-28  7:29         ` Johannes Berg
2008-10-26 20:44     ` John W. Linville
2008-10-26 22:12     ` Marcel Holtmann
2008-10-28 15:13 ` Bob Copeland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] wireless: fix regression caused by regulatory config option' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).