From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: add DFS CAC time parameter
Date: Tue, 20 May 2014 20:24:33 +0200 [thread overview]
Message-ID: <1400610273.4474.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140520180832.GD13981@tuxdriver.com> (sfid-20140520_201518_644762_1B148A19)
On Tue, 2014-05-20 at 14:08 -0400, John W. Linville wrote:
> > I can add support for version 19 and 20 in one crda. I am not sure
> > this is the best option.
> > BTW what about versions < 19? How do we handle this this days?
>
> What about older CRDA with newer wireless-regdb? Do we need to worry about that?
I think we should, but if we can't then at least can we cut to an
extensible format?
(and yeah, I know I was part of defining the format ...)
johannes
next prev parent reply other threads:[~2014-05-20 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 8:40 [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic
2014-05-09 8:40 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-05-20 7:33 ` [PATCH] wireless-regdb: add DFS CAC time parameter Luis R. Rodriguez
2014-05-20 13:26 ` Janusz Dziedzic
2014-05-20 14:24 ` John W. Linville
2014-05-20 18:01 ` Janusz Dziedzic
2014-05-20 18:08 ` John W. Linville
2014-05-20 18:24 ` Johannes Berg [this message]
2014-05-20 18:48 ` Luis R. Rodriguez
2014-05-21 16:03 ` Johannes Berg
2014-05-21 18:00 ` John W. Linville
2014-05-21 19:09 ` Johannes Berg
2014-06-09 7:33 ` Janusz Dziedzic
2014-06-10 16:45 ` Johannes Berg
2014-06-09 8:00 ` Felix Fietkau
2014-06-09 10:22 ` Janusz Dziedzic
2014-06-09 12:27 ` Janusz Dziedzic
2014-06-10 16:46 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2014-02-12 18:54 [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic
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=1400610273.4474.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).