> 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.
If you want to put a subdir of one arch into another wouldn't it be rather cleaner to use arm/arm/aarch64/ as your architecture base ? Alan -- 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/