No - we do not want another symlink.Create something like:include/i386/kabi-asm/ <= i386 specific filesinclude/kabi/ <= general files

Then we can do:LINUXINCLUDE += -Iinclude/kabi-$(ARCH)And the following would work like expected:#include <kabi/foo.h>#include <kabi-asm/foo.h>

But this leaves all existing users in the dark cold.So a more involved approach could be to tkae the opposite approach.To dedicate an area for kernel only header files and make sure thisdirectory is searched _before_ include/

We could do something likekinclude/linux/ <= generic kernel include headerskinclude/$(arch)/asm/ <= arch specific include headers

would actually cut it.Then we would not hurt existing users since they continue to useinclude/linux/* + include/asm/*And we could migrate one by one to the kernel clean part.In other words - a solution that keeps backwards compatibility.A solution that distingush hard between what is the ABI andwhat is kernel stuff.And a namespace that is not in use today.

And we have so many users of include/linux today. They do not needa _kabi_ prefix so let it go.