linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <linville@tuxdriver.com>, <johannes@sipsolutions.net>
Cc: <easwar.krishnan@atheros.com>, <linux-wireless@vger.kernel.org>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 0/7] cfg80211: few regulatory fixes and debugging enhancements
Date: Wed, 20 Oct 2010 10:18:52 -0700	[thread overview]
Message-ID: <1287595139-10761-1-git-send-email-lrodriguez@atheros.com> (raw)

Easwar reported some odd issues with ath9k regarding regulatory
while during the 2.6.36-rc cycles. Unfortunately I was only able
to address the issues for these reported issues until now as I had
other higher priority items on my plate. It turns out that some of
these issues are pretty serious, mostly the one that does not apply
regulatory updates for disabling a band when that is the intention.

These issues were simply overlooked but they are part of the design,
so we target a few of these fixes to stable. The new debugging stuff
is left only for the development series on the next kernel.

There is one world regulatory domain update we are considering now
for the Atheros cards, but we haven't yet decided on this. I'll send
the patch if we agree on it next. Thanks to Easwar for his reports
and work on this.

Luis R. Rodriguez (7):
  cfg80211: pass the reg hint initiator to helpers
  cfg80211: fix allowing country IEs for WIPHY_FLAG_STRICT_REGULATORY
  cfg80211: fix disabling channels based on hints
  cfg80211: add debug prints for when we ignore regulatory hints
  cfg80211: add debug print when disabling a channel on a custom regd
  cfg80211: add debug print when processing a channel
  cfg80211: prefix REG_DBG_PRINT() with cfg80211

 include/linux/nl80211.h |    6 ++-
 include/net/cfg80211.h  |   15 +++---
 net/wireless/reg.c      |  133 +++++++++++++++++++++++++++++++++++++++++------
 3 files changed, 130 insertions(+), 24 deletions(-)


             reply	other threads:[~2010-10-20 17:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 17:18 Luis R. Rodriguez [this message]
2010-10-20 17:18 ` [PATCH 1/7] cfg80211: pass the reg hint initiator to helpers Luis R. Rodriguez
2010-10-20 17:18 ` [PATCH 2/7] cfg80211: fix allowing country IEs for WIPHY_FLAG_STRICT_REGULATORY Luis R. Rodriguez
2010-10-20 21:24   ` Gábor Stefanik
2010-10-20 17:18 ` [PATCH 3/7] cfg80211: fix disabling channels based on hints Luis R. Rodriguez
2010-10-20 17:18 ` [PATCH 4/7] cfg80211: add debug prints for when we ignore regulatory hints Luis R. Rodriguez
2010-10-20 17:18 ` [PATCH 5/7] cfg80211: add debug print when disabling a channel on a custom regd Luis R. Rodriguez
2010-10-20 17:18 ` [PATCH 6/7] cfg80211: add debug print when processing a channel Luis R. Rodriguez
2010-10-21  8:18   ` Senthil Balasubramanian
2010-10-21  9:02     ` Luis R. Rodriguez
2010-10-21  9:04       ` Luis R. Rodriguez
2010-10-20 17:18 ` [PATCH 7/7] cfg80211: prefix REG_DBG_PRINT() with cfg80211 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=1287595139-10761-1-git-send-email-lrodriguez@atheros.com \
    --to=lrodriguez@atheros.com \
    --cc=easwar.krishnan@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).