From: "Arend van Spriel" <arend@broadcom.com>
To: "Vladimir Kondratiev" <qca_vkondrat@qca.qualcomm.com>
Cc: "Julian Calaby" <julian.calaby@gmail.com>,
"John W . Linville" <linville@tuxdriver.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v0 0/2] driver for 60g Wilocity chip wil6210
Date: Thu, 11 Oct 2012 11:09:26 +0200 [thread overview]
Message-ID: <50768CC6.5050007@broadcom.com> (raw)
In-Reply-To: <3023056.XLicri5zy7@lx-vladimir>
On 10/11/2012 08:35 AM, Vladimir Kondratiev wrote:
> On Thursday, October 11, 2012 09:51:28 AM Julian Calaby wrote:
>> Hi Vladimir,
>>
>> On Thu, Oct 11, 2012 at 5:23 AM, Vladimir Kondratiev
>>
>> <qca_vkondrat@qca.qualcomm.com> wrote:
>>> Hi,
>>>
>>> Here goes driver for the "wil6210" chip by Wilocity.
>>>
>>
>> Whilst I'm sure that this driver will end up being kernel quality
>> code, as this is an initial development snapshot, have you considered
>> putting it in "staging" until it's mostly feature complete?
>>
>
> Hi,
>
> Sure I asked this very question before submitting. Luis advised to go for
> the regular location, not "staging". I am pretty neutral about what location
> is better, so I just follow recommendations on this matter.
>
> Thanks, Vladimir.
From my own experiences I got the impression that the staging directory
was more about learning the development process and converting a
proprietary driver with all kind of abstractions for multi-OS support to
a native linux driver. So I would agree with Luis, but you could have
used RFC instead of PATCH to draw more attention to this although the
'60g' term will trigger that as well.
Regards,
AvS
prev parent reply other threads:[~2012-10-11 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:23 [PATCH v0 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-10-10 18:23 ` [PATCH v0 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-10-10 18:23 ` [PATCH v0 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
2012-10-10 22:51 ` [PATCH v0 0/2] driver for 60g Wilocity chip wil6210 Julian Calaby
2012-10-11 6:35 ` Vladimir Kondratiev
2012-10-11 9:09 ` Arend van Spriel [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=50768CC6.5050007@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--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).