From: Joe Perches <joe@perches.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Stefano Brivio <stefano.brivio@polimi.it>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mb@bu3sch.de, zajec5@gmail.com
Subject: Re: [PATCH net-next] MAINTAINERS: b43 updates
Date: Thu, 24 Jun 2010 16:57:09 -0700 [thread overview]
Message-ID: <1277423829.1654.111.camel@Joe-Laptop.home> (raw)
In-Reply-To: <4C23EFDE.3000702@lwfinger.net>
On Thu, 2010-06-24 at 18:53 -0500, Larry Finger wrote:
> I never said that b43 is unmaintained. It is definitely getting much
> more than "odd fixes".
If Stefano isn't maintaining it, who is?
next prev parent reply other threads:[~2010-06-24 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 23:30 [PATCH 0/3] b43: logging cleanups Joe Perches
[not found] ` <cover.1276988387.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2010-06-19 23:30 ` [PATCH 1/3] drivers/net/wireless/b43: Use local ratelimit_state Joe Perches
2010-06-19 23:30 ` [PATCH 2/3] drivers/net/wireless/b43: Logging cleanups Joe Perches
2010-06-19 23:30 ` [PATCH 3/3] drivers/net/wireless/b43: Rename b43_debug to b43_debugging Joe Perches
2010-06-24 18:53 ` [PATCH 0/3] b43: logging cleanups John W. Linville
[not found] ` <20100624185339.GC2368-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2010-06-24 19:20 ` Larry Finger
2010-06-24 19:40 ` Joe Perches
2010-06-24 19:56 ` Larry Finger
2010-06-24 23:45 ` [PATCH net-next] MAINTAINERS: b43 updates Joe Perches
2010-06-24 23:53 ` Larry Finger
2010-06-24 23:57 ` Joe Perches [this message]
[not found] ` <1277423829.1654.111.camel-AkRN8/LKpobuYGix6ZUp1Q@public.gmane.org>
2010-06-25 2:41 ` Larry Finger
[not found] ` <4C241770.6030701-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2010-06-25 13:22 ` Michael Büsch
2010-06-25 13:28 ` [PATCH 0/3] b43: logging cleanups Michael Büsch
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=1277423829.1654.111.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
--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).