From: "John W. Linville" <linville@tuxdriver.com>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Luis Correia <luis.f.correia@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Johannes Berg <johannes@sipsolutions.net>,
Jarek Poplawski <jarkao2@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
David Miller <davem@davemloft.net>
Subject: Re: [announce] new rt2800 drivers for Ralink wireless & project tree
Date: Wed, 4 Nov 2009 10:15:06 -0500 [thread overview]
Message-ID: <20091104151505.GE12965@tuxdriver.com> (raw)
In-Reply-To: <4AF09A15.3060504@gmail.com>
On Tue, Nov 03, 2009 at 10:01:09PM +0100, Gertjan van Wingerde wrote:
> However, it is good to see that you have put effort in providing a patch series
> for these issues.
Yes, indeed. Thanks to Bart for making patches available!
> Now, since I believe that it is better to work with people, rather than against
> them, would it be possible to post this patch series somewhere as a set of
> separate patches, so that they can be reviewed as such?
I must echo this request.
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-11-04 15:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:51 [announce] new rt2800 drivers for Ralink wireless & project tree Bartlomiej Zolnierkiewicz
2009-11-03 21:00 ` Ivo van Doorn
2009-11-03 21:44 ` Bartlomiej Zolnierkiewicz
2009-11-03 22:01 ` Ivo van Doorn
2009-11-03 22:34 ` Bartlomiej Zolnierkiewicz
2009-11-03 23:09 ` Gertjan van Wingerde
2009-11-03 23:46 ` Bartlomiej Zolnierkiewicz
2009-11-04 1:33 ` Julian Calaby
2009-11-04 1:33 ` Julian Calaby
2009-11-04 2:28 ` Bartlomiej Zolnierkiewicz
2009-11-03 23:48 ` Alan Cox
2009-11-03 23:48 ` Alan Cox
2009-11-03 23:52 ` Bartlomiej Zolnierkiewicz
2009-11-04 0:40 ` Alan Cox
2009-11-04 0:48 ` Bartlomiej Zolnierkiewicz
2009-11-04 8:37 ` Ingo Molnar
2009-11-04 14:38 ` John W. Linville
2009-11-04 14:38 ` John W. Linville
2009-11-04 21:51 ` Ivo van Doorn
2009-11-04 22:12 ` John W. Linville
2009-11-04 22:12 ` John W. Linville
2009-11-06 7:46 ` Pavel Machek
2009-11-06 7:46 ` Pavel Machek
2009-11-06 17:58 ` Ivo van Doorn
2009-11-06 18:30 ` Bartlomiej Zolnierkiewicz
2009-11-06 18:30 ` Bartlomiej Zolnierkiewicz
2009-11-06 18:59 ` John W. Linville
2009-11-07 17:30 ` Pavel Machek
2009-11-07 17:30 ` Pavel Machek
2009-11-07 18:12 ` Luis Correia
2009-11-07 18:31 ` Ivo van Doorn
2009-11-07 18:31 ` Ivo van Doorn
2009-11-07 19:43 ` Luis R. Rodriguez
2009-11-03 21:01 ` Gertjan van Wingerde
2009-11-03 21:01 ` Gertjan van Wingerde
2009-11-04 15:15 ` John W. Linville [this message]
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=20091104151505.GE12965@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=jarkao2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.