> > What if the include/linux files themselves make use of the asm files?
> >
>
> No, not acceptable.
>
> The thing is, trying to redefine the old namespaces is hopeless at this
> point. Hence the proposed new namespace <linux/abi/*.h> ...
> <linux/abi/arch/*.h> would be my preference for an arch-specific
> subnamespace.
>
> Thus the rule is:
>
> a) <linux/abi/*> files MUST NOT include files outside <linux/abi/*>
>
> b) <linux/*.h> and <asm/*.h> are legacy namespaces. They should be
> considered to be completely different in kernel and userspace -- in
> effect, glibc will eventually ship with its own set of these headers.
>
> c) <linux/abi/*> files should be clean for inclusion from either kernel
> or userspace.
>
The only issue that we might have, is that <linux/abi/*> will once
again break many things. Sure, if we have to fix them once to get
this fixed for good, why not.
On the other hand, why not leave it at <linux/*.h> and <asm/*.h>
as the location of the ABI, and then move all kernel only
related stuff to <kernel/*.h> (or whatever, just the concept which
count ...) which can then include whatever it needs form the other
places (linux/asm)?
Regards,
-- Martin Schlemmer
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/