From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Brett Rudley <brudley@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Roland Vossen <rvossen@broadcom.com>,
Alwin Beukers <alwin@broadcom.com>,
"gregkh@suse.de" <gregkh@suse.de>
Subject: Re: [PATCH v3] move brcm80211 drivers to mainline
Date: Wed, 5 Oct 2011 10:24:03 -0400 [thread overview]
Message-ID: <20111005142402.GC17286@tuxdriver.com> (raw)
In-Reply-To: <4E8C64EF.3070203@broadcom.com>
On Wed, Oct 05, 2011 at 04:08:47PM +0200, Arend van Spriel wrote:
> With number of cleanup patch series merged in by Greg KH, I'd like to
> once again propose moving brcm80211 out of staging and into mainline.
>
> I've put together a patch to add a copy of the current sources from
> staging-next into drivers/net/wireless/brcm80211 of the wireless-next
> repository.
>
> The patch is somewhat large, so I've posted the patch at:
>
> http://linuxwireless.org/en/users/Drivers/brcm80211?action=AttachFile&do=view&target=0001-net-wireless-add-brcm80211-drivers-v3.patch
Feel free to complain, but I plan to merge this in time for the merge
window unless someone identifies a true "showstopper" problem with
this patch in the next day or so.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-10-05 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:08 [PATCH v3] move brcm80211 drivers to mainline Arend van Spriel
2011-10-05 14:24 ` John W. Linville [this message]
2011-10-06 18:18 ` Greg KH
2011-10-05 14:56 ` Johannes Berg
2011-10-05 15:34 ` Arend Van Spriel
2011-10-05 15:06 ` Hauke Mehrtens
2011-10-05 15:40 ` Arend Van Spriel
2011-10-05 15:44 ` Larry Finger
2011-10-05 16:38 ` Arend Van Spriel
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=20111005142402.GC17286@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=alwin@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=frankyl@broadcom.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.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.