linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: The new regulatory code kills my wireless
Date: Fri, 12 Sep 2008 13:34:38 -0700	[thread overview]
Message-ID: <20080912203438.GB7722@tesla> (raw)
In-Reply-To: <1221250959.5576.10.camel@johannes.berg>

On Fri, Sep 12, 2008 at 01:22:38PM -0700, Johannes Berg wrote:
> On Fri, 2008-09-12 at 12:19 -0700, Luis R. Rodriguez wrote:
> > Well no, IMHO people *should not* use the old regulatory stuff if
> > possible, the idea is to kill it ASAP, you should only use the old
> > regulatory stuff if you *need* to, meaning you have some dependency
> > on the old module parameter for some strange odd ball reason or if
> > you cannot compile and install crda or iw.
> 
> Well, TBH, I was just too lazy to do that ;)

Sorry, I forgot to factor in lazy people, that's important. I hope
there are no lazy distributions.

  Luis

  reply	other threads:[~2008-09-12 20:34 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
2008-09-12 19:19     ` Luis R. Rodriguez
2008-09-12 20:22       ` Johannes Berg
2008-09-12 20:34         ` Luis R. Rodriguez [this message]
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=20080912203438.GB7722@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=Luis.Rodriguez@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).