All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Richard Farina <sidhayn@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-regdb: flaw in general functionality
Date: Tue, 25 Nov 2008 19:35:54 -0500	[thread overview]
Message-ID: <1227659754.2556.11.camel@dv> (raw)
In-Reply-To: <20081126001942.GN5950@tesla>

On Tue, 2008-11-25 at 16:19 -0800, Luis R. Rodriguez wrote:

> This is documented here:
> 
> http://wireless.kernel.org/en/developers/Regulatory#Changingthedatabasefileformat

I mean, I don't know how painful it can be.  Perhaps it's better to
anticipate some requirements earlier than to change them later.  I think
both "don't transmit" and "don't transmit unless permitted by the AP"
could be useful in some jurisdictions.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2008-11-26  0:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 22:32 wireless-regdb: flaw in general functionality Richard Farina
2008-11-24 23:12 ` Luis R. Rodriguez
2008-11-24 23:21   ` Pavel Roskin
2008-11-24 23:26     ` Luis R. Rodriguez
2008-11-25  2:26       ` Richard Farina
2008-11-25  2:31         ` Pavel Roskin
2008-11-26  0:19           ` Luis R. Rodriguez
2008-11-26  0:35             ` Pavel Roskin [this message]
2008-11-26  1:02               ` Luis R. Rodriguez
2008-11-26  3:10                 ` Richard Farina
2008-11-26 17:05                   ` Luis R. Rodriguez
2008-11-26  5:53                 ` Michael Renzmann
2008-11-26 17:17                   ` Luis R. Rodriguez
2008-11-26 19:55                     ` Michael Renzmann
2008-11-26 20:04                       ` Johannes Berg
2008-11-27  5:26                         ` Michael Renzmann
2008-11-26 17:19                   ` Johannes Berg

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=1227659754.2556.11.camel@dv \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=sidhayn@gmail.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.