[RFC][PATCH 0/2] KABI example conversion and cleanup

[Arjan van de Ven]

\
> This is true for a small enough application. But things grow, libraries 
> are added, and includes keep pulling other includes in. Sooner or later 
> you'll have a collision.
> > The problem is things like u64 etc that is VERY common in all headers,
> > but then again __u64 etc are just fine, history has proven that already.
> >   
> Agree. But to be on the safe side one can use uint64_t and friends 
> (which the kernel can typedef to u64 and first degree relatives)


actually uint64_t is a bigger namespace pollution than __u64 ;)