From: "John W. Linville" <linville@tuxdriver.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: torvalds@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl, rodriguez@atheros.com,
johannes@sipsolutions.net
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config option
Date: Sun, 26 Oct 2008 16:09:39 -0400 [thread overview]
Message-ID: <20081026200939.GC12648@tuxdriver.com> (raw)
In-Reply-To: <20081026103024.2712ddc9@infradead.org>
On Sun, Oct 26, 2008 at 10:30:24AM -0700, Arjan van de Ven wrote:
> From 9095a0f6005a8f50c79e51f4aaceda95e361a891 Mon Sep 17 00:00:00 2001
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Sun, 26 Oct 2008 10:25:30 -0700
> Subject: [PATCH] wireless: fix regression caused by regulatory config option
>
> The default for the regulatory compatibility option is wrong;
> if you picked the default you ended up with a non-functional wifi
> system (at least I did on Fedora 9 with iwl4965).
> I don't think even the October 2008 releases of the various distros
> has the new userland so clearly the default is wrong, and also
> we can't just go about deleting this in 2.6.29...
>
> Change the default to "y" and also adjust the config text a little to
> reflect this.
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?
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-26 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 17:30 [PATCH] wireless: fix regression caused by regulatory config option Arjan van de Ven
2008-10-26 20:09 ` John W. Linville [this message]
2008-10-26 20:16 ` Linus Torvalds
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081026200939.GC12648@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arjan@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rodriguez@atheros.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.