From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
Gary Zambrano <zambrano@broadcom.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
bcm43xx-dev@lists.berlios.de, ralf@linux-mips.org
Subject: Re: Merging SSB upstream
Date: Sun, 6 May 2007 11:44:27 +0200 [thread overview]
Message-ID: <200705061144.27817.mb@bu3sch.de> (raw)
In-Reply-To: <20070506020051.GA30917@tuxdriver.com>
On Sunday 06 May 2007 04:00:51 John W. Linville wrote:
> On Sun, May 06, 2007 at 03:03:17AM +0200, Michael Buesch wrote:
> > So, now that mac80211 is merged upstream, I think it's
> > time to merge SSB and the b44-ssb port upstream.
> > Note that bcm43xx-mac80211 is _not_ ready for upstream, yet.
>
> ACK, unfortunately.
>
> > What do you think? I'd like to merge ssb as-is, although
> > the embedded-device parts are not quite finished, yet.
> > But they don't interfere with the non-embedded parts used
> > by b44 and the bcm43xx PCI cards.
>
> How much testing have you (and others) done w/ b44?
Well, it works for me with my b44 card I got from broadcom.
There are really only 2 or 3 different b44 cards, so chances are damn
high it will work for all.
> I had to remove
> the b44 ssb changes from fedora because a) users reported problems;
Which problems were that? The 2 compile issues?
Trivial to fix if that's the only issue. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2007-05-06 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 1:03 Merging SSB upstream Michael Buesch
2007-05-06 2:00 ` John W. Linville
2007-05-06 9:44 ` Michael Buesch [this message]
2007-05-06 17:38 ` John W. Linville
2007-05-06 18:44 ` Michael Buesch
2007-05-06 3:11 ` Jeff Garzik
2007-05-06 9:41 ` Michael Buesch
2007-05-07 16:43 ` Gary Zambrano
2007-05-07 20:35 ` Michael Buesch
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=200705061144.27817.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=zambrano@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 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).