> There is, however, a reason *not* to do it which should be carefully > considered: by co-locating the compatibility version with the modern > version, it gets access to static functions that are part of the > implementation of the modern version. If we move the compatibility > versions out, it may entail having to export those statics. > > -hpa Hmm, do I hear a reason to simply fully #include the (newly separated) old-style .c file from within the new-style .c file? Not necessarily a wonderful approach, but perhaps it beats doing a "correct full separation" and thus having a couple new-born (and unhappy ;) exports any day? Andreas Mohr -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
