All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: John Linville <linville@tuxdriver.com>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: The new regulatory code kills my wireless
Date: Fri, 12 Sep 2008 13:46:36 -0500	[thread overview]
Message-ID: <48CAB90C.5090302@lwfinger.net> (raw)
In-Reply-To: <20080912174036.GC6134@tesla>

Luis R. Rodriguez wrote:
> On Fri, Sep 12, 2008 at 10:37:26AM -0700, Larry Finger wrote:
>> After pulling the latest git from wireless-testing, my wireless
>> failed. I bisected this to be commit
>> 544ec9a11fdef5142a76a8eb4b186a80a272c035, "cfg80211: Add new wireless
>> regulatory infrastructure".
--snip--
> 
> Please apply johill's patch, "[PATCH] cfg80211: fix regdomain macro"

That patch fixed the problem. For someone following this thread, the 
patch is by Johannes Berg.

I can understand when some oddball hardware causes a corner-case 
problem - I just had one with an ancient laptop - but somehow, I 
expect that most people will use the old regulatory option, at least 
for a while. Shouldn't the most rudimentary testing have caught this 
problem?

Larry

  reply	other threads:[~2008-09-12 18:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 17:37 The new regulatory code kills my wireless Larry Finger
2008-09-12 17:40 ` Luis R. Rodriguez
2008-09-12 18:46   ` Larry Finger [this message]
2008-09-12 19:19     ` Luis R. Rodriguez
2008-09-12 20:22       ` Johannes Berg
2008-09-12 20:34         ` Luis R. Rodriguez
2008-09-12 20:59           ` Larry Finger
2008-09-12 21:15             ` Luis R. Rodriguez
2008-09-13  2:26         ` Marcel Holtmann
2008-09-13  8:33           ` Johannes Berg
2008-09-13 16:51             ` Marcel Holtmann
2008-09-14  0:52               ` John W. Linville

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=48CAB90C.5090302@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.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 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.