On Sat, Mar 06, 2021 at 06:55:41PM +0800, Jiaxun Yang wrote: > > > On Sat, Mar 6, 2021, at 5:53 PM, Thomas Bogendoerfer wrote: > [...] > > Just to understand you, you want > > > > arch/mips/include/asm/loongson/2ef > > arch/mips/include/asm/loongson/32 > > arch/mips/include/asm/loongson/64 > > Yeah it looks reasonable but from my point of view doing these movement > brings no actual benefit :-( oh it does for sure. There will no more build errors for non loogson configs for things like #include <loongson_regs.h> because it will not work for loongson either. And it will be clear, which of the 3 loongson.h is used. Which then gives chances for even more cleanups. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
