From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v1] Fix for regulatory in 60g
Date: Wed, 12 Sep 2012 11:39:02 +0200 [thread overview]
Message-ID: <1347442742.4293.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <14825905.k5l7QPk6IR@lx-vladimir>
On Wed, 2012-09-12 at 11:10 +0300, Vladimir Kondratiev wrote:
> > I don't really see a reason for that given that we don't have a driver
> > that uses 60g support anyway. Why should I pick it up anyway this late
> > in the cycle?
> Well, it is bug fix for 60g band that was merged.
It was, but it never gets used.
> Also, I am readying
> driver for 60g card and will submit it shortly.
That won't be making it into 3.6 either though.
> Having this bug fixed
> will help to 3-rd parties that want to experiment with 60g,
> and for 60g-related work in tools like wpa_supplicant and iw.
So I don't think this makes much sense? They'll probably use compat
anyway ;-)
I'll apply the patch to my -next branch after Luis reviews it.
johannes
prev parent reply other threads:[~2012-09-12 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 11:52 [PATCH v1] Fix for regulatory in 60g Vladimir Kondratiev
2012-09-11 11:52 ` [PATCH v1] cfg80211: Fix regulatory check for 60GHz band frequencies Vladimir Kondratiev
2012-09-13 19:03 ` Luis R. Rodriguez
2012-09-11 17:23 ` [PATCH v1] Fix for regulatory in 60g Johannes Berg
2012-09-12 8:10 ` Vladimir Kondratiev
2012-09-12 9:39 ` Johannes Berg [this message]
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=1347442742.4293.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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).