From: Michael Buesch <mb@bu3sch.de>
To: linux-wireless@vger.kernel.org
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Fwd: b43legacy maintainer needed
Date: Tue, 23 Oct 2007 11:22:32 +0200 [thread overview]
Message-ID: <200710231122.32585.mb@bu3sch.de> (raw)
Forwarding this to more public places. :)
---------- Forwarded Message ----------
Subject: b43legacy maintainer needed
Date: Tuesday 23 October 2007
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Broadcom Linux <bcm43xx-dev@lists.berlios.de>
As you have seen in a previous E-mail, I have resigned as maintainer of bcm43xx and b43legacy. No
replacement will be needed for bcm43xx as it will not be in the kernel much longer.
The effort required to maintain b43legacy should be minimal. For the past several months, most of
what I have done is take b43 patches written by Michael Buesch and port them to b43legacy.
Besides the obvious programming experience, the maintainer should have a BCM4306/2 card. If you have
a laptop with a PCMCIA slot, I have an extra Linksys WPC54G with that chip that you could have.
If you are interested, please write to me.
Thanks,
Larry
-------------------------------------------------------
--
Greetings Michael.
reply other threads:[~2007-10-23 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200710231122.32585.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).