From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: "John W. Linville" <linville@tuxdriver.com>,
Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felix Fietkau <nbd@openwrt.org>, John Walker <john@x109.net>,
Krishna Chaitanya <chaitanya.mgit@gmail.com>,
netfilter-devel@vger.kernel.org,
Richard Fontana <fontana@sharpeleven.org>
Subject: Re: Parser stable fix question for CFG80211_INTERNAL_REGDB
Date: Tue, 1 Jul 2014 11:54:43 -0700 [thread overview]
Message-ID: <CAB=NE6W4yg2_290aKacM0ar63yoVt_G8h59iWGxfCanV+AM=vA@mail.gmail.com> (raw)
In-Reply-To: <20140701171713.GO27687@wotan.suse.de>
On Tue, Jul 1, 2014 at 10:17 AM, Luis R. Rodriguez <mcgrof@suse.com> wrote:
>> How is this any different from any other kernel support issue?
>
> This is a build issue that does not cause any errors, users go through with the install
> just fine and only at run time do they discover the issue. We never documented
> the expecations nor do I think we expected this before. This is also caused by an
> input file from userspace, I do consider the issue unexpected.
This is a bit more broken given that DFS CAC patches are upstream but
we haven't yet even provided the removal of antenna gain on the awk
script but for some reason it did add the DFS CAC parsing to the awk
script, so upstream has the awk DFS CAC parser options, we don't yet
even use it, and the antenna gain wasn't removed. I'll work on that
patch but parsing things in awk is getting a bit hairy for the
conditionals. We can use the C parser now that we have on but the DFS
CAC stuf was not yet ironed out for CRDA and wireless-regdb...
Luis
next prev parent reply other threads:[~2014-07-01 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 18:55 Parser stable fix question for CFG80211_INTERNAL_REGDB Luis R. Rodriguez
2014-06-30 19:19 ` Luis R. Rodriguez
[not found] ` <CAB=NE6VTN==Ewvf4HhTcadWLzjZnYkF1xSM1Yej6QfotWHKY0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-01 14:41 ` John W. Linville
[not found] ` <20140701144149.GB6358-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-07-01 17:17 ` Luis R. Rodriguez
2014-07-01 18:54 ` Luis R. Rodriguez [this message]
2014-07-01 20:18 ` John W. Linville
2014-07-02 7:33 ` Krishna Chaitanya
2014-07-02 12:04 ` Maxime Bizon
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='CAB=NE6W4yg2_290aKacM0ar63yoVt_G8h59iWGxfCanV+AM=vA@mail.gmail.com' \
--to=mcgrof@suse.com \
--cc=chaitanya.mgit@gmail.com \
--cc=fontana@sharpeleven.org \
--cc=gregkh@linuxfoundation.org \
--cc=janusz.dziedzic@tieto.com \
--cc=johannes@sipsolutions.net \
--cc=john@x109.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
--cc=netfilter-devel@vger.kernel.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).