public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Joe Perches <joe@perches.com>
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,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: [PATCH net-next] MAINTAINERS: b43 updates
Date: Thu, 24 Jun 2010 21:41:52 -0500	[thread overview]
Message-ID: <4C241770.6030701@lwfinger.net> (raw)
In-Reply-To: <1277423829.1654.111.camel@Joe-Laptop.home>

On 06/24/2010 06:57 PM, Joe Perches wrote:
> 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?

We are working on that.

Larry

  reply	other threads:[~2010-06-25  2:41 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
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
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
2010-06-25  2:41             ` Larry Finger [this message]
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=4C241770.6030701@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=joe@perches.com \
    --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=netrolller.3d@gmail.com \
    --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