* Steven Rostedt ([EMAIL PROTECTED]) wrote: > Recently I've been doing some work that will affect both the i386 and x86_64 > architectures. So there will be common code for both, as well as code > that will be unique for the specific arch. So I was looking into a way > to do this cleanly, and found that there is no clean way to share code > between x86_64 and i386.
Thanks for taking this on. I'm sure Andi has a bunch of ideas on this topic, but it would be nice to see the consolidation. > So the move patches are a simple move of one file, with the slight exception > of files that hold the speedstep-lib.h file. This file was moved from the > arch/i386/kerne/cpu/cpufreq directory and put into the include/asm-i386 > directory. This was due to the fact that some of the moved files included > it, and some files that were not moved also included it. Instead of using > the #include "../../x86/" hack again, I just simply moved it to the global > i386 include directory. Only the arch/x86 will use the include/asm-i386 what about asm-x86/ dir? the asm/ symlink would still point to relevant arch, but the file there could be simply #include <asm-x86/file.h> ? thanks, -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
