On Tue, 10 Jul 2018, Andy Shevchenko wrote: > On Fri, Jul 6, 2018 at 12:50 AM, <hpa@xxxxxxxxx> wrote: > > > For things exported to user space use __u* and __s* types... the _t types would actually violate the C standard with respect to namespace pollution. > > Hmm... Coding style 5(d) allows to use uintNN_t in new code (as a > variation of uNN choice). But not for user space exposed headers. See 5(e) for that matter. Thanks, tglx
