On Tue, May 17, 2011 at 8:58 AM, Keith Berkoben <berkoben@xxxxxxxxx> wrote: > Thanks! > > When following this process (it has a couple steps...), is it generally a > true statement that changes from > wireless-testing->wireless-next-->net-next-->etc. are usually pushed by > "Merges", or should I also be watching for changes filtering through in > other ways? > > Stated another way, is the heuristic of: > 1. look for patch in wireless-testing > 2. look for subsequent Merge of that branch (or parent) in wireless-next > 3. look for subsequent Merge of wireless-next branch in net-next > 4. repeat all the way to the build I want > and effective way to ensure what I want is in a build without reading all of > the individual source files in each archive? Patches go first into wireless-next, then stable stuff goes into wirless-2.6 (current RC), and then both of these get pulled into wireless-testing, which provides the RC fixes + the next bits, on a stable kernel (RC). Compat-wireless daily snapshots use linux-next so changes take a bit to propagate there. OpenWrt uses wireless-testing as the base tree, you can tell by loading the compat module, it will tell you the base tree and git tree tags that was used as source. 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
