On Thu, Oct 06, 2011 at 01:08:02PM -0400, John W. Linville wrote: > Alright then, I'll plan on proceeding with this "soon" (since I'm > taking a long weekend). What about F14? Should I leave it with the > separate package stuff? Go ahead and integrate the compat-wireless > bits into the base kernel package? Or just leave it alone? "What to do about f14" is something we've been asking a lot lately. We've already decided we're not rebasing, and we're not going to be backporting every fix, so the answer for the most part has been "sorry, try f15/f16", which is a pretty crap response from the users point of view, but hopefully we'll not fall back into this mistake of sitting on a year old codebase again. The -longterm releases are a great idea in theory, but when you think about what they're actually doing (replicating the workload of an enterprise kernel, but with a handful people at most), it's pretty obvious that you can't rely on them to fix everything. So to answer your question: if you want to do compat-wireless in f14, fine. If you want to backport wireless.git to it, fine. At the end of the day, you get the bugs that result from drivers/net/wireless/ so whatever that code ends up being, it's your doing.. :-) Dave _______________________________________________ kernel mailing list kernel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kernel