From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Janusz Dziedzic <janusz.dziedzic@tieto.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: Wed, 21 May 2014 21:09:16 +0200 [thread overview]
Message-ID: <1400699356.4136.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140521180020.GA13656@tuxdriver.com>
On Wed, 2014-05-21 at 14:00 -0400, John W. Linville wrote:
> The 'do not parse more permissively' would seem to be a problem if
> we still produce an older format too, no? I mean, wouldn't we have
> to simply drop new rules to produce an older binary? Even worse if
> we left the old binary in place, since then you could never update
> any rules for old crda installations at all.
That's true, in a sense.
> It seems like forcing a crda update to use any new format-breaking
> rules might just be the right thing. Can we make crda choke and die
> loudly when it sees an unknown format? Will the current crda do that?
It will, yes. If the version number is mismatched it'll print "Invalid
database version" (to stderr) and exit.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: add DFS CAC time parameter
Date: Wed, 21 May 2014 21:09:16 +0200 [thread overview]
Message-ID: <1400699356.4136.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140521180020.GA13656@tuxdriver.com>
On Wed, 2014-05-21 at 14:00 -0400, John W. Linville wrote:
> The 'do not parse more permissively' would seem to be a problem if
> we still produce an older format too, no? I mean, wouldn't we have
> to simply drop new rules to produce an older binary? Even worse if
> we left the old binary in place, since then you could never update
> any rules for old crda installations at all.
That's true, in a sense.
> It seems like forcing a crda update to use any new format-breaking
> rules might just be the right thing. Can we make crda choke and die
> loudly when it sees an unknown format? Will the current crda do that?
It will, yes. If the version number is mismatched it'll print "Invalid
database version" (to stderr) and exit.
johannes
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2014-05-21 19:09 UTC|newest]
Thread overview: 37+ 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 ` [wireless-regdb] " Janusz Dziedzic
2014-05-09 8:40 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-05-09 8:40 ` [wireless-regdb] " Janusz Dziedzic
2014-05-20 7:33 ` [PATCH] wireless-regdb: add DFS CAC time parameter Luis R. Rodriguez
2014-05-20 7:33 ` [wireless-regdb] " Luis R. Rodriguez
2014-05-20 13:26 ` Janusz Dziedzic
2014-05-20 13:26 ` [wireless-regdb] " Janusz Dziedzic
2014-05-20 14:24 ` John W. Linville
2014-05-20 14:24 ` [wireless-regdb] " John W. Linville
2014-05-20 18:01 ` Janusz Dziedzic
2014-05-20 18:01 ` [wireless-regdb] " Janusz Dziedzic
2014-05-20 18:08 ` John W. Linville
2014-05-20 18:08 ` [wireless-regdb] " John W. Linville
2014-05-20 18:24 ` Johannes Berg
2014-05-20 18:24 ` [wireless-regdb] " Johannes Berg
2014-05-20 18:48 ` Luis R. Rodriguez
2014-05-20 18:48 ` [wireless-regdb] " Luis R. Rodriguez
2014-05-21 16:03 ` Johannes Berg
2014-05-21 16:03 ` [wireless-regdb] " Johannes Berg
2014-05-21 18:00 ` John W. Linville
2014-05-21 18:00 ` [wireless-regdb] " John W. Linville
2014-05-21 19:09 ` Johannes Berg [this message]
2014-05-21 19:09 ` Johannes Berg
2014-06-09 7:33 ` Janusz Dziedzic
2014-06-09 7:33 ` [wireless-regdb] " Janusz Dziedzic
2014-06-10 16:45 ` Johannes Berg
2014-06-10 16:45 ` [wireless-regdb] " Johannes Berg
2014-06-09 8:00 ` Felix Fietkau
2014-06-09 8:00 ` [wireless-regdb] " Felix Fietkau
2014-06-09 10:22 ` Janusz Dziedzic
2014-06-09 10:22 ` [wireless-regdb] " Janusz Dziedzic
2014-06-09 12:27 ` Janusz Dziedzic
2014-06-09 12:27 ` [wireless-regdb] " Janusz Dziedzic
2014-06-10 16:46 ` Johannes Berg
2014-06-10 16:46 ` [wireless-regdb] " 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=1400699356.4136.13.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 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.