It is no coincidence that the 802.11 subsystem now has had no regressions for 2.6.33 and 2.6.34 (thanks to Rafael for keeping track of these). I don't think its that we haven't been doing a lot of development, instead I think a lot of it has to do with the fact that we have been aggressively engaged with stable after we were slapped about this at our last wireless summit. There's a few patches which I realize still do fall through the crack or due to time we haven't yet backported. I have been subscribed the stable-review list [1] for a few kernel releases and I think the process for review for stable is a bit overwhelming and I can only thank you so much for the great work you guys do at juggling all these patches together. The main reason I see some patches still fall through the cracks is due to some patches not being marked stable on the commit log entry or the patch requiring some manual backport for the latest stable or for other older stable series. To aid with this for the 802.11 subsystem I've created a wiki page we can use for this purpose: http://wireless.kernel.org/en/developers/stable-pending If you are either a user or developer and you feel a patch is important for stable which meet the above criteria please be sure to mark it there. Help with manual backports are also appreciated as we sometimes cannot address these due to time. [1] http://linux.kernel.org/mailman/listinfo/stable-review Luis -- 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
