From: James Ketrenos <jketreno@linux.intel.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jouni Malinen <jkmaline@cc.hut.fi>, netdev@oss.sgi.com
Subject: Re: [PATCH] ieee80211 subsystem
Date: Tue, 08 Feb 2005 17:33:26 -0600 [thread overview]
Message-ID: <42094C46.9040701@linux.intel.com> (raw)
In-Reply-To: <42094A6D.9080508@pobox.com>
Jeff Garzik wrote:
> Just to keep everything moving, my recommendation would be to move the
> code to net/*, and resend the patch (with whatever changes you have
> made to date).
>
> That way you, and others, can review and work on the tree in parallel.
>
> I'm worried that your list of todo items (based on responses so far)
> is already so long that I won't hear from you for another year ;-) We
> need to get the wireless-2.6 tree active again, and avoid
> bottlenecks. We need "release early, release often."
I've allocated a couple hours tomorrow to merge in all the comments to
date and get them pushed to my bk tree (bk://ipw.bkbits.net/ipw-2.6 is
where I've been staging all of the ipw work)
So, I'll send a new patch out tomorrow with what I have to date.
James
next prev parent reply other threads:[~2005-02-08 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 18:47 [PATCH] ieee80211 subsystem James Ketrenos
2005-02-04 22:48 ` Jeff Garzik
2005-02-05 6:07 ` Randy.Dunlap
2005-02-08 3:57 ` Jouni Malinen
2005-02-08 9:41 ` James Ketrenos
2005-02-05 8:13 ` Christoph Hellwig
2005-02-08 2:49 ` Randy.Dunlap
2005-02-08 8:24 ` James Ketrenos
2005-02-10 4:36 ` Randy.Dunlap
2005-02-08 4:29 ` Jouni Malinen
2005-02-08 9:26 ` James Ketrenos
2005-02-08 23:25 ` Jeff Garzik
2005-02-08 23:33 ` James Ketrenos [this message]
2005-02-11 0:49 ` James Ketrenos
2005-02-11 21:44 ` Jeff Garzik
2005-02-08 4:45 ` Randy.Dunlap
2005-02-08 19:13 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 21:45 Jean Tourrilhes
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=42094C46.9040701@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=netdev@oss.sgi.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 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.