From: "John W. Linville" <linville@tuxdriver.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: James Ketrenos <jketreno@linux.intel.com>,
Stephen Clark <Stephen.Clark@seclark.us>,
ipw3945-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, Axj <axjslack@bluebottle.com>
Subject: Re: [ipw3945-devel] Request for help...
Date: Wed, 25 Jul 2007 10:46:51 -0400 [thread overview]
Message-ID: <20070725144651.GA7093@tuxdriver.com> (raw)
In-Reply-To: <46A69359.4030201@garzik.org>
On Tue, Jul 24, 2007 at 08:03:37PM -0400, Jeff Garzik wrote:
> Though in fairness, I am a bit disappointed that wireless-dev seems to
> occasionally become a resting place for drivers, rather than just a pit
> stop on the way to upstream. In particular, stuff still has not been
> moved out of drivers/net/wireless/mac80211 and into
> drivers/net/wireless, which is a basic and easy step to get all code
> ready for upstream.
Point taken. I'll apply a series of patches to eliminate the extra
directory. I guess I'll rename the existing bcm43xx and zd1211rw
drivers in wireless-dev as a temporary measure until those ports are
done upstream.
I would definitely like to see more action from mac80211 driver
developers towards getting drivers upstream. With mac80211 merged,
I know of no reason not to get the drivers ready for upstream now so
they can funnel through netdev-2.6 into -mm with plenty of time to
spare before the next merge window.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-25 15:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29 ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30 ` John W. Linville
2007-07-24 21:13 ` Jeff Garzik
2007-07-25 1:15 ` James Ketrenos
2007-07-25 0:03 ` Jeff Garzik
2007-07-25 0:30 ` Stephen Clark
2007-07-25 0:35 ` David Miller
2007-07-25 0:43 ` Stephen Clark
2007-07-25 0:46 ` David Miller
2007-07-25 1:05 ` Stephen Clark
2007-07-25 1:18 ` David Miller
2007-07-25 1:23 ` Jeff Garzik
2007-07-25 1:29 ` Stephen Clark
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 0:45 ` Maurizio Monge
2007-07-25 1:35 ` Jeff Garzik
2007-07-25 8:01 ` James Ketrenos
2007-07-25 14:50 ` John W. Linville
2007-07-27 12:36 ` Jeff Garzik
2007-07-25 14:46 ` John W. Linville [this message]
2007-07-25 15:19 ` Jeff Garzik
2007-07-25 9:32 ` Zhu Yi
2007-07-26 15:10 ` Axj
2007-07-26 16:22 ` Pavel Roskin
2007-07-27 6:34 ` Axj
2007-07-27 7:44 ` Zhu Yi
2007-07-27 8:48 ` Axj
[not found] ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27 8:56 ` Zhu Yi
2007-07-27 9:10 ` Axj
2007-07-30 0:58 ` Zhu Yi
2007-08-01 6:40 ` Axj
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=20070725144651.GA7093@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Stephen.Clark@seclark.us \
--cc=axjslack@bluebottle.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@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 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.