From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W . Linville" <linville@tuxdriver.com>,
Joe Perches <joe@perches.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v10 0/3] wireless: Driver for 60GHz card wil6210
Date: Thu, 13 Dec 2012 12:51:16 -0800 [thread overview]
Message-ID: <20121213205116.GQ15974@pogo> (raw)
In-Reply-To: <2874864.eaglUHDoO0@lx-vladimir>
On Wed, Dec 12, 2012 at 06:25:06PM +0200, Vladimir Kondratiev wrote:
> On Wednesday, December 12, 2012 05:04:38 PM Johannes Berg wrote:
> > On Wed, 2012-12-12 at 17:47 +0200, Vladimir Kondratiev wrote:
> >
> > > Vladimir Kondratiev (3):
> > > wireless: Driver for 60GHz card wil6210
> >
> > Since you didn't want to hear my objections on the iftype usage ...
> > maybe you should not Cc me any more.
> >
> > johannes
> >
>
> Johannes,
>
> I do hear it, and I agree with it!!!
>
> I will work to support this new
> iftype, PBSS, properly. I just don't have enough data to do it right
> now. Thus, I want initial driver for the 1-st ever 60g card to be merged;
> this will serve as test bed for the next framework modifications.
>
> I recall, you was asking me why do I pushing to do 60g related
> infrastructure changes when no one driver exists. I want to address this
> and then return to the infrastructure.
>
> Let's have at least something working as 1-st step. Now, I need to assemble
> all pieces of the puzzle:
>
> - initial infrastructure (done)
> - minimal driver (these patches)
> - tools (wpa_supplicant partially done, other patches sent; iw - partially done)
> - regulatory - patches submitted.
>
> Then, when minimal support will be in place, I can handle new features.
>
> Hope it explain why I want to merge minimal driver 1-st.
Vladimir, please only enable monitor support and STA mode to
be used on the upstream driver submission. If you want PCP mode
you'll have to address Johannes' concerns. If you want to enable
PCP mode as you have you can enable it by enabling it through an
extra crap/ category patch on compat-drivers.
Luis
next prev parent reply other threads:[~2012-12-13 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 15:47 [PATCH v10 0/3] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 1/3] " Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 2/3] wil6210: Local compensation for dynamic hexdump Vladimir Kondratiev
2012-12-12 15:56 ` Luis R. Rodriguez
2012-12-13 7:45 ` [PATCH] wil6210: alternative functions " Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 3/3] wireless: integrate wil6210 driver into build Vladimir Kondratiev
2012-12-12 16:04 ` [PATCH v10 0/3] wireless: Driver for 60GHz card wil6210 Johannes Berg
2012-12-12 16:25 ` Vladimir Kondratiev
2012-12-13 20:51 ` Luis R. Rodriguez [this message]
2012-12-16 12:29 ` [PATCH v11] " Vladimir Kondratiev
2012-12-19 7:55 ` Vladimir Kondratiev
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=20121213205116.GQ15974@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=joe@perches.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@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).