On Tue, Apr 2, 2013 at 2:23 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > I only addressed what compat-drivers-... had a few days ago. > > However, I simplified the system a bit. I don't have any snapshot, but I > did announce the git tree. Grab that, run ./gentree.py against > linux-next and you should get something. Then you will have to hack up > the Kconfig (backport/compat/Kconfig) and include files > (backport/include/*), presumably. Or you can wait until we merge. At this point I'm freezing development on compat and compat-drivers to merge all this work onto Johannes' tree. > If you're interested in alx, you'd have to add that -- look at the > copy-list.alx file for that. Johannes already committed a few things here, I'll be sure to test it as well. > I hope that soon enough Luis might cut some testing releases from this > though. Absolutely, full steam ahead, just give us a few days. I should note that RHEL / SUSE / Debian all had the same issues -- running into symbols we are exporting with the same upstream name. The move to use LINUX_BACKPORT() should help cure these issues in general moving forward. Additionally if you really want to help in this area please review commit 8ae96730 on compat.git specifically Andi Kleen's work on module namespace. If we can figure out to support module namespace *ourselves*, ie, without Linus having to carry this crap around, then we'd solve all these issues easily, I believe we wouldn't have to rely on LINUX_BACKPORT() and in fact that would also mean renaming our *driver* symbols. This means for instance you can run one drivers with your stock mac80211, another with the backported version, should you ever have to support such crazy environement. Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
