From: "John W. Linville" <linville@tuxdriver.com>
To: netdev@vger.kernel.org
Subject: Wireless patches to push for 2.6.18?
Date: Fri, 26 May 2006 15:59:00 -0400 [thread overview]
Message-ID: <20060526195855.GD32487@tuxdriver.com> (raw)
As David M. so recently reminded us, 2.6.17 is likely to be blessed soon.
That will open a short merge window for non-"fixes" to go into 2.6.18.
Along w/ the patches currently on the 'upstream' branch, I'd like to
see some of the the drivers hanging-out only on the 'master' branch
of wireless-2.6 to get polished-up and pushed-out. What do you think
are the best candidates?
http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/master/
Anyone have anything else they are holding-back for 2.6.18? What about
the wireless button infrastructure Ivo posted yesterday? Is that
useful for any of the drivers currently in wireless-2.6?
I was caught a bit 'flat-footed' for the 2.6.17 merge window.
I'd like to be prepared for this one... :-)
Thanks!
John
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2006-05-26 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 19:59 John W. Linville [this message]
2006-05-26 22:17 ` Wireless patches to push for 2.6.18? Michael Buesch
2006-05-28 7:37 ` Stefano Brivio
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=20060526195855.GD32487@tuxdriver.com \
--to=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 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.