From: "Henry Ptasinski" <henryp@broadcom.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Michael Büsch" <mb@bu3sch.de>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"mcgrof@infradead.org" <mcgrof@infradead.org>,
"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: [PATCH 8/8] compat-wireless: add brcm80211 driver
Date: Mon, 13 Sep 2010 21:18:11 -0700 [thread overview]
Message-ID: <4C8EF783.2050901@broadcom.com> (raw)
In-Reply-To: <AANLkTin5mGf51p39Cje_ZpRvjH6LKo2xG4QLiw4W-ybo@mail.gmail.com>
On 09/12/2010 02:34 PM, Luis R. Rodriguez wrote:
> On Sun, Sep 12, 2010 at 10:36 AM, Gábor Stefanik
> <netrolller.3d@gmail.com> wrote:
>> On Sun, Sep 12, 2010 at 7:29 PM, Michael Büsch<mb@bu3sch.de> wrote:
>>> On Sun, 2010-09-12 at 19:16 +0200, Gábor Stefanik wrote:
>>>> Umm... do we accept staging drivers in compat-wireless?
>>>
>>> Why shouldn't we accept them in compat?
>>>
>>> --
>>> Greetings Michael.
>>>
>>>
>>
>> Dunno, just given the general hostility of the wireless team towards
>> staging drivers.
>
> The idea is to enable users, so I'll gladly accept them, thanks
> haukes, I'll apply after first reviewing your other series.
>
I was going to try and figure out the compat-wireless changes needed to
enable brcm80211 myself, so the quick contribution on this is much
appreciated by me if nobody else.
- Henry
next prev parent reply other threads:[~2010-09-14 4:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 16:18 [PATCH 0/8 v2] compat-wireless: ath9kl and compat_autoconf.h fixes Hauke Mehrtens
2010-09-11 16:18 ` Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 1/8] compat-wireless: handle depending on something build as module Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 2/8] compat-wireless: make atk6kl build with older kernels Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 3/8] compat-wireless: fix for CONFIG_WIRELESS_EXT=n Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 4/8] compat-wireless: build if kernel does not have mac80211 Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 5/8] compat-wireless: add conditions form config into compat_autoconf.h Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 6/8] compat-wireless: Add warning if wext is deactivated Hauke Mehrtens
2010-09-12 20:20 ` Johannes Berg
2010-09-12 20:35 ` Hauke Mehrtens
2010-09-12 21:09 ` Hauke Mehrtens
2010-10-02 16:55 ` [PATCH] compat-wireless: introduce driver-select group for atlxx Walter Goldens
[not found] ` <362796.1111.qm@web56806.mail.re3.yahoo.com>
2010-10-05 19:11 ` Luis R. Rodriguez
2010-10-05 19:14 ` Luis R. Rodriguez
2010-09-12 21:11 ` [PATCH 6/8 v2] compat-wireless: Add warning if wext is deactivated Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 7/8] compat-wireless: remove special handling for CONFIG_CFG80211_WEXT Hauke Mehrtens
2010-09-11 16:18 ` [PATCH 8/8] compat-wireless: add brcm80211 driver Hauke Mehrtens
2010-09-12 17:16 ` Gábor Stefanik
2010-09-12 17:29 ` Michael Büsch
2010-09-12 17:36 ` Gábor Stefanik
2010-09-12 21:34 ` Luis R. Rodriguez
2010-09-14 4:18 ` Henry Ptasinski [this message]
2010-09-13 18:27 ` [PATCH 0/8 v2] compat-wireless: ath9kl and compat_autoconf.h fixes Luis R. Rodriguez
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=4C8EF783.2050901@broadcom.com \
--to=henryp@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mb@bu3sch.de \
--cc=mcgrof@infradead.org \
--cc=netrolller.3d@gmail.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 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.