Hopefully you saw davem's similarly titled post... I don't see much in the -next patches I've had in wireless-testing over the last few days that is a big deal for 2.6.37. Those that do seem important are fixes that can still go anyway. Stephen usually asks not to have anything in the trees during the merge window that isn't intended for Linus. So I'm going to reset wireless-next-2.6 back to where it was for the last pull done by davem. I will also remove those patches from wireless-testing just to avoid being out of sync -- the fixes will be back soon, and the others will be back after the close of the merge window. I will be merging the fixes and sending them to davem during the window -- feel free to identify anything you think I might miss. Also, as I have mentioned previously, I intend to start rebasing wireless-testing after each merge window. As it stands today, the history is too much of a mess to be useful for bisection anyway. I hope everyone can handle a once-per-release rebase of wireless-testing. John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
