From: Jeff Garzik <jeff@garzik.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
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
Subject: Re: Merging SSB upstream
Date: Sat, 05 May 2007 23:11:44 -0400 [thread overview]
Message-ID: <463D4770.9060903@garzik.org> (raw)
In-Reply-To: <200705060303.17594.mb@bu3sch.de>
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.
>
> 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.
> So we _could_ remove the ssb-mips code, but I don't like to
> do that for better maintainability. It doesn't hurt anyone IMO.
What does Ralf (MIPS maintainer) and Gary (Broadcom maintainer) think?
For my part, I'm not going to render even a tentative opinion without a
link to actual code.
Last I saw of the code, and descriptions in IRC, it sounded sane.
Jeff
next prev parent reply other threads:[~2007-05-06 3:11 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
2007-05-06 17:38 ` John W. Linville
2007-05-06 18:44 ` Michael Buesch
2007-05-06 3:11 ` Jeff Garzik [this message]
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=463D4770.9060903@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.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).