untangle asm/termios.h-related headers
At that point we have the following picture:
* architectures with uapi/asm/termios.h will have include
of <asm/termios.h> resolve to that
* architectures without such file (other than loongarch)
will have it resolve to generated/uapi/asm/termios.h consisting of
include/asm-generic/termios.h, which consists of
include/uapi/asm-generic/termios.h
* loongarch will have it resolve to generated/asm/termios.h
consisting of #include <asm-generic/termios.h>, then as above.
It's still too convoluted; to untangle that we can just remove
include/asm-generic/termios.h and tell loongarch to stop bothering
with generated/asm/termios.h.
That way the rules become:
* architectures with uapi/asm/termios.h will have include
of <asm/termios.h> resolve to that
* architectures without such file will have it resolve to
generated/uapi/asm/termios.h consisting of #include <asm-generic/termios.h>
which will resolve to include/uapi/asm-generic/termios.h
IOW, same result with fewer intermediate steps and the rules that
are easier to follow - asm/termios.h *always* refers to an UAPI
header, either native or default one.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2 files changed
