From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: Wireless patches to push for 2.6.18?
Date: Sat, 27 May 2006 00:17:27 +0200 [thread overview]
Message-ID: <200605270017.27373.mb@bu3sch.de> (raw)
In-Reply-To: <20060526195855.GD32487@tuxdriver.com>
On Friday 26 May 2006 21:59, John W. Linville wrote:
> 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?
Yes, we would like to merge the big tx-power-rewrite (aka get 4318
working) into the bcm43xx driver, but it is only 90% completed atm.
I guess we still have 1 to 1.5 weeks left, before the window closes?
next prev parent reply other threads:[~2006-05-26 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 19:59 Wireless patches to push for 2.6.18? John W. Linville
2006-05-26 22:17 ` Michael Buesch [this message]
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=200605270017.27373.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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;
as well as URLs for NNTP newsgroup(s).