From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: David Miller <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linville@tuxdriver.com
Subject: Re: pull request: wireless-next-2.6 2009-10-28
Date: Thu, 29 Oct 2009 21:45:07 +0200 [thread overview]
Message-ID: <84144f020910291245l1a7a3fd6o8822ecd4ce3b5504@mail.gmail.com> (raw)
In-Reply-To: <200910291514.40318.bzolnier@gmail.com>
Hi Bart,
On Thu, Oct 29, 2009 at 4:14 PM, Bartlomiej Zolnierkiewicz
<bzolnier@gmail.com> wrote:
>> lots of cleanups to the staging drivers, why not direct some of that
>> energy to the drivers/net/wireless ones?
>
> When did we start to apply "fix it yourself" rule instead of "submitter
> should fix it" one to the _new_ code..
Don't be silly, I didn't say that.
I was simply pointing out that your time would probably be better
spent in improving the "proper" ralink wireless drivers but if you
_really_ prefer to spend your time in pointless arguments, go ahead.
It should be pretty obvious by now that the best way to improve things
is to work with the relevant maintainers, not against them. (Unless
you wish your work to be ignored, of course.)
Pekka
next prev parent reply other threads:[~2009-10-29 19:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 21:10 John W. Linville
2009-10-28 21:56 ` Bartlomiej Zolnierkiewicz
2009-10-29 11:12 ` Bartlomiej Zolnierkiewicz
2009-10-29 12:15 ` David Miller
2009-10-29 12:45 ` Bartlomiej Zolnierkiewicz
2009-10-29 12:59 ` David Miller
2009-10-29 13:35 ` Bartlomiej Zolnierkiewicz
2009-10-29 13:52 ` Pekka Enberg
2009-10-29 14:14 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:21 ` David Miller
2009-10-29 14:39 ` Michael Buesch
2009-10-29 14:44 ` Gertjan van Wingerde
2009-10-29 14:48 ` Michael Buesch
2009-10-29 15:08 ` Luis R. Rodriguez
2009-10-29 17:49 ` Bartlomiej Zolnierkiewicz
2009-10-29 19:45 ` Pekka Enberg [this message]
2009-10-29 21:48 ` Bartlomiej Zolnierkiewicz
2009-10-30 5:59 ` Pekka Enberg
2009-10-30 7:00 ` Johannes Berg
2009-10-30 11:06 ` Jarek Poplawski
2009-10-30 15:02 ` John W. Linville
2009-10-30 20:44 ` Jarek Poplawski
2009-11-01 19:04 ` Bartlomiej Zolnierkiewicz
2009-11-02 9:10 ` Ingo Molnar
2009-11-02 9:23 ` Johannes Berg
2009-11-02 10:07 ` Ingo Molnar
2009-11-02 17:01 ` John W. Linville
2009-11-02 17:32 ` Luis Correia
2009-11-02 17:36 ` Randy Dunlap
2009-11-02 18:29 ` John W. Linville
2009-11-02 18:43 ` Ivo van Doorn
2009-11-03 19:59 ` Bartlomiej Zolnierkiewicz
2009-11-03 20:32 ` Ivo van Doorn
2009-11-03 21:04 ` Bartlomiej Zolnierkiewicz
2009-11-02 21:16 ` Pavel Machek
2009-11-04 13:03 ` Jiri Kosina
2009-11-04 21:17 ` Ivo van Doorn
2009-11-04 22:00 ` Pavel Machek
2009-11-04 22:09 ` John W. Linville
2009-11-02 16:46 ` John W. Linville
2009-10-30 15:14 ` John W. Linville
2009-10-29 13:53 ` David Miller
2009-10-29 14:13 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:20 ` David Miller
2009-10-29 14:24 ` Johannes Berg
2009-10-29 14:34 ` Bartlomiej Zolnierkiewicz
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=84144f020910291245l1a7a3fd6o8822ecd4ce3b5504@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=bzolnier@gmail.com \
--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
all inboxes | Powered by JetHome®