From: Michael Buesch <mb@bu3sch.de>
To: David Miller <davem@davemloft.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2009-10-08
Date: Fri, 9 Oct 2009 10:57:19 +0200 [thread overview]
Message-ID: <200910091057.21269.mb@bu3sch.de> (raw)
In-Reply-To: <20091008.180119.242402327.davem@davemloft.net>
On Friday 09 October 2009 03:01:19 David Miller wrote:
> From: Michael Buesch <mb@bu3sch.de>
> Date: Fri, 9 Oct 2009 01:08:06 +0200
>
> > I was planning to do a better solution, but I didn't have the time, yet.
>
> The change is harmless while we're twiddling our thumbs waiting
> for you to implement the fix "properly."
>
> Not having the fix in is a developer burdon because people turn
> on the DMA API debugger and are going to keep reporting it's
> complaints here and elsewhere.
>
> Get over your Napoleon complex, and let reasonable working fixes
> get into the tree even if you don't find them optimal. You can
> always improve them later, "when you get around to it."
>
> People put fixes in without my ACK in my areas of expertiece all
> the time. I got over it a long time ago, it's OK, and not worth
> stressing out over.
Ok, that's enough. If you do not need a maintainer, then work without one.
What's a maintainer good for, if it's not for maintaining the code quality?
The patch needlessly moves huge chunks of crap, adds stupid comments, wastes memory.
If that's what you want just to remove a debugging message on devices that virtually
nobody owns, so be it.
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
--- wireless-testing.orig/MAINTAINERS
+++ wireless-testing/MAINTAINERS
@@ -1066,7 +1066,6 @@ F: include/net/ax25.h
F: net/ax25/
B43 WIRELESS DRIVER
-M: Michael Buesch <mb@bu3sch.de>
M: Stefano Brivio <stefano.brivio@polimi.it>
L: linux-wireless@vger.kernel.org
W: http://linuxwireless.org/en/users/Drivers/b43
--
Greetings, Michael.
next prev parent reply other threads:[~2009-10-09 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 22:34 pull request: wireless-2.6 2009-10-08 John W. Linville
2009-10-08 23:08 ` Michael Buesch
2009-10-08 23:16 ` Michael Buesch
2009-10-09 0:55 ` David Miller
2009-10-09 1:01 ` David Miller
2009-10-09 8:57 ` Michael Buesch [this message]
2009-10-09 9:18 ` David Miller
2009-10-09 13:23 ` John W. Linville
2009-10-09 13:49 ` Michael Buesch
2009-10-09 0:52 ` David Miller
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=200910091057.21269.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).