On Tue, Apr 2, 2013 at 12:49 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > >> dma-buf was added via commit d15bd7ee on v3.3 but completed >> in a more sound fassion in later kernels, you should preferably >> be at v3.5 a least, so we take the latest dma-buf implementation >> and port it for usage on kernels [3.0-3.4]. We take the >> implementation as of next-20130328. > > I'm curious about that approach -- I noticed it a few times already, > e.g. with CONFIG_AVERAGE, however... > > If you don't mangle symbols (you don't), then wouldn't this cause > linking errors when you try to load compat.ko on say kernel 3.0? Did you see the usage of LINUX_BACKPORT() on the header file? That would rename the exported symbols, and the header we carry makes sure the kernel's original is not used, that means that our DRM code would use our backport_*() symbols instead. Not sure, perhaps I'm missing something? 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
