On Fri, May 02, 2008 at 04:04:52PM -0500, Scott White wrote: > > >Was this patch series in time for the 2.6.26 merge window? > > > >If not, please consider merging at least the following patches since > >they are real bugfixes: > > > >> rt2x00: Don't enable short preamble for 1MBs > >> rt2x00: Fix quality/activity led handling > >> rt2x00: Clarify supported chipsets in Kconfig > > > >The others are code cleanups which are "nice to have", but could otherwise > >wait for 2.6.27. > > The merge window is still open at this time. I haven't seen > a rc1 yet. Anyway I saw that only the 3 bugfixes are currently > in the queue. As the owner of several (10 by the university and > 2 personal) rt73 usb wireless cards, I would really like it if the > latest version 2.1.5 made into 2.6.26. As someone who has used 2.6.24 > and finished compiling 2.6.25 two days ago I find that the driver in > both kernels is not good. Not good means I get a wireless signal and > I get data transfers, but the speed fluctuates and have other issues. > However with each release, the problems I have are slowing decreasing. > I have been waiting patiently for 2.6.25-rc1 to have 2.1.5 since 2.1.5 > was announced. I really think all of 2.1.5 should get in 2.6.25-rc1. I'm sorry, but this isn't how the merge window is used. The merge window is for merging code that is _already_ pending when the window opens. No one should wait for the merge window to open before sending code to the upstream maintainers. (I'm not suggesting that Ivo delayed on purpose, I'm just stating the policy.) Anything that fixes an actual bug can still go to 2.6.26 over the next several weeks. But code that is simply new development will have to wait for 2.6.27's merge window before it gets to Linus. Thanks, John -- John W. Linville linville@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
