Arnd, On Mon, Jul 09, 2012 at 04:32:11PM +0100, Arnd Bergmann wrote: > We have a lot of reviewers that are familiar with the 32 bit code, so > I think the main strategy should be to spot duplicate code early > and make sure we deal with it individually. Examples for this are > probably the implementations for kvm and perf, which largely deal > with the same hardware on both architectures. Those definitely must > not get duplicated into mostly-identical files. In many cases, we're > moving those things into drivers/*, in other cases we might want to > use Makefile logic to include a sub-directory from one arch into another, > as we do for arch/um.
I don't see why we would need to get a subdir from one into the other. If the SoCs would need some common drivers (like GPIO), they should go into drivers/ anyway. There is some perf code that could be shared (though not building a subdir as we have different instruction sets) but I would like that moved to a more generic place. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/