Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net,
	marcel@holtmann.org, kalle.valo@nokia.com, kyle@mcmartin.ca
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 5/5] cfg80211: default OLD_REG to n
Date: Fri, 20 Feb 2009 01:04:34 -0500	[thread overview]
Message-ID: <1235109874-3966-6-git-send-email-lrodriguez@atheros.com> (raw)
In-Reply-To: <1235109874-3966-1-git-send-email-lrodriguez@atheros.com>

Since we are not following the schedule to remove OLD_REG by 2.6.29
lets simply set it to default to n for 2.6.30 and schedule its
removal for 2.6.31

Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
 Documentation/feature-removal-schedule.txt |    5 +++--
 net/wireless/Kconfig                       |    2 +-
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index ac98851..bf83b02 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -7,7 +7,7 @@ be removed from this file.
 ---------------------------
 
 What:	old static regulatory information and ieee80211_regdom module parameter
-When:	2.6.29
+When:	2.6.31
 Why:	The old regulatory infrastructure has been replaced with a new one
 	which does not require statically defined regulatory domains. We do
 	not want to keep static regulatory domains in the kernel due to the
@@ -19,7 +19,8 @@ Why:	The old regulatory infrastructure has been replaced with a new one
 	and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was
 	set. We also kept around the ieee80211_regdom module parameter in case
 	some applications were relying on it. Changing regulatory domains
-	can now be done instead by using nl80211, as is done with iw.
+	can now be done instead by using nl80211, as is done with iw, or
+	wpa_supplicant.
 Who:	Luis R. Rodriguez <lrodriguez@atheros.com>
 
 ---------------------------
diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig
index e28e2b8..009f5b8 100644
--- a/net/wireless/Kconfig
+++ b/net/wireless/Kconfig
@@ -25,7 +25,7 @@ config NL80211
 
 config WIRELESS_OLD_REGULATORY
 	bool "Old wireless static regulatory definitions"
-	default y
+	default n
 	---help---
 	  This option enables the old static regulatory information
 	  and uses it within the new framework. This is available
-- 
1.6.0.3


  parent reply	other threads:[~2009-02-20  6:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  6:04 [PATCH 0/5] cfg80211: enhance world roaming Luis R. Rodriguez
2009-02-20  6:04 ` [PATCH 1/5] cfg80211: enable active-scan / beaconing on Ch 1-11 for world regdom Luis R. Rodriguez
2009-02-20 19:59   ` Gábor Stefanik
2009-02-20 20:08     ` Luis R. Rodriguez
2009-02-20  6:04 ` [PATCH 2/5] cfg80211: enable 5 GHz world roaming channels Luis R. Rodriguez
2009-02-20  6:04 ` [PATCH 3/5] cfg80211: Add AP beacon regulatory hints Luis R. Rodriguez
2009-02-20 17:06   ` Johannes Berg
2009-02-20 20:34     ` Luis R. Rodriguez
2009-02-20  6:04 ` [PATCH 4/5] ath9k: follow beacon hints on reg_notifier when world roaming Luis R. Rodriguez
2009-02-20  6:04 ` Luis R. Rodriguez [this message]
2009-02-20  6:08 ` [PATCH 0/5] cfg80211: enhance " Luis R. Rodriguez

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=1235109874-3966-6-git-send-email-lrodriguez@atheros.com \
    --to=lrodriguez@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@nokia.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox