From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Francis Moreau" <francis.moro@gmail.com>,
"Arend van Spriel" <arend@broadcom.com>,
linux-wireless@vger.kernel.org, gregkh@suse.de
Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set"
Date: Tue, 13 Sep 2011 13:44:16 -0500 [thread overview]
Message-ID: <4E6FA480.5030500@lwfinger.net> (raw)
In-Reply-To: <20110913174444.GG11772@tuxdriver.com>
On 09/13/2011 12:44 PM, John W. Linville wrote:
>
> We are going to have to find a way to get brcmsmac into the
> wireless-next tree to make it feasible for the Broadcom guys to get
> bcma support into that driver. Do you agree?
>
> We could move it under the drivers/net/wireless tree. Or, maybe I
> could negotiate with Greg to keep it under the drivers/staging tree
> but to let me manage it under wireless-next. Or...? Do you have
> any thoughts on this?
Based on the earlier comments, I still see lots of problems in getting brcmsmac
into the drivers/net/wireless tree; however, the solution where Greg lets you
manage that part of drivers/staging does not seem to cause too many problems, as
long as he is kept in the loop. If you could push those changes through Greg
rather than DaveM, I don't think he would lose any control.
Larry
next prev parent reply other threads:[~2011-09-13 18:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:46 About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set" Francis Moreau
2011-09-12 21:27 ` Rafał Miłecki
2011-09-13 7:03 ` Francis Moreau
2011-09-13 13:28 ` John W. Linville
2011-09-13 13:37 ` Francis Moreau
2011-09-13 13:44 ` John W. Linville
2011-09-13 20:25 ` Rafał Miłecki
2011-09-14 6:53 ` Francis Moreau
2011-09-14 9:27 ` Arend Van Spriel
2011-09-14 9:11 ` Arend Van Spriel
2011-09-14 9:15 ` Francis Moreau
2011-09-16 7:29 ` Rafał Miłecki
2011-09-13 17:44 ` John W. Linville
2011-09-13 18:44 ` Larry Finger [this message]
2011-09-13 19:10 ` John W. Linville
2011-09-13 20:23 ` Rafał Miłecki
2011-09-14 8:42 ` Greg KH
2011-09-16 10:43 ` Rafał Miłecki
2011-09-16 10:52 ` Arend Van Spriel
2011-09-16 10:55 ` Rafał Miłecki
2011-09-16 11:13 ` Arend van Spriel
2011-09-16 11:20 ` Rafał Miłecki
2011-09-16 11:25 ` Arend van Spriel
2011-09-16 11:34 ` Rafał Miłecki
2011-09-14 9:23 ` Arend Van Spriel
2011-09-14 20:18 ` Rafał Miłecki
2011-09-15 11:53 ` Arend van Spriel
2012-01-11 11:40 ` Francis Moreau
2012-01-11 12:24 ` Arend van Spriel
2012-01-11 13:13 ` Francis Moreau
2012-01-11 14:26 ` Arend van Spriel
2012-01-11 14:30 ` Francis Moreau
2012-01-11 15:41 ` Francis Moreau
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=4E6FA480.5030500@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=francis.moro@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@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.