From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Joe Perches <joe@perches.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 0/3] b43: logging cleanups
Date: Thu, 24 Jun 2010 14:20:58 -0500 [thread overview]
Message-ID: <4C23B01A.6020901@lwfinger.net> (raw)
In-Reply-To: <20100624185339.GC2368@tuxdriver.com>
On 06/24/2010 01:53 PM, John W. Linville wrote:
> On Sat, Jun 19, 2010 at 04:30:08PM -0700, Joe Perches wrote:
>> Just some small cleanups
>>
>> Joe Perches (3):
>> drivers/net/wireless/b43: Use local ratelimit_state
>> drivers/net/wireless/b43: Logging cleanups
>> drivers/net/wireless/b43: Rename b43_debug to b43_debugging
>
> Any of the b43 guys want to express an opinion on these?
The local ratelimit patch is OK. My personal opinion is that the others
are just churning the source for no real reason, but I have no major
objections.
Larry
next prev parent reply other threads:[~2010-06-24 19:20 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 [this message]
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
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=4C23B01A.6020901@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=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