From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Greg KH" <greg@kroah.com>, "Greg KH" <gregkh@suse.de>,
"Francis Moreau" <francis.moro@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Michael Buesch" <mb@bu3sch.de>
Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set"
Date: Thu, 15 Sep 2011 13:53:45 +0200 [thread overview]
Message-ID: <4E71E749.5020402@broadcom.com> (raw)
In-Reply-To: <CACna6rzK86LQ4bULMvcfTTwtDxAGtDzc8K+uGobarnkOpax17w@mail.gmail.com>
On 09/14/2011 10:18 PM, Rafał Miłecki wrote:
> W dniu 14 września 2011 11:23 użytkownik Arend Van Spriel
> <arend@broadcom.com> napisał:
>> For my bcma integration effort (which is already stale due to our brcmsmac cleanup) I simply took "wireless-next" bcma using meld. Was surprised that I also needed to do this for ssb as there are some include dependencies. In early bcma discussions a strong preference was given (by Michael if I am correct) to keep bcma independent from ssb at the cost of some duplication. For include files this preference might be less strong, but I still think it is a good idea to have these chip interconnect bus drivers independent from each other.
> The code is independent, if some includes are not, that should be
> reported& fixed.
No problem. Will look into it.
Gr. AvS
next prev parent reply other threads:[~2011-09-15 11:53 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
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 [this message]
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=4E71E749.5020402@broadcom.com \
--to=arend@broadcom.com \
--cc=francis.moro@gmail.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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 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).