linux-kernel - Re: [RFC] Using C99 stdint vs kernel __uX types in kernel drmUAPI (was Re: [PATCH 1/2] Revert "include/uapi/drm/amdgpu_drm.h: use __u32 and _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.SOC.2.00.1608221348530.19914@sibernet.com>
Date:   Mon, 22 Aug 2016 14:12:00 -0700 (PDT)
From:   randyf@...ernet.com
To:     Emil Velikov <emil.l.velikov@...il.com>
cc:     Rob Clark <robdclark@...il.com>,
        Mikko Rapeli <mikko.rapeli@....fi>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        ML dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [RFC] Using C99 stdint vs kernel __uX types in kernel drmUAPI
 (was Re: [PATCH 1/2] Revert "include/uapi/drm/amdgpu_drm.h: use __u32 and
 __u64 from <linux/types.h>")


On Mon, 22 Aug 2016, Emil Velikov wrote:

> Although last time around people leaned towards the __uX types, if we
> have a consensus amongst drm (kernel) developers about using stdint
> ones everything should be fine.
> We just need a handful of acks from the different maintainers.
>

   My opinion (as a non-Linux driver maintainer) is to use the stdint 
variants.  They are (or at least should be) supported by all OS's 
and compilers without any special modifications.


   That said, it really isn't that hard for me to wrap the __uX types 
either.


 	---- Randy