mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: randyf@sibernet.com
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Rob Clark <robdclark@gmail.com>,
	Mikko Rapeli <mikko.rapeli@iki.fi>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ML dri-devel <dri-devel@lists.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>")
Date: Mon, 22 Aug 2016 14:12:00 -0700 (PDT)	[thread overview]
Message-ID: <alpine.SOC.2.00.1608221348530.19914@sibernet.com> (raw)
In-Reply-To: <CACvgo52Hj-V=8juG7ukYaLOJMowsaMtwMYWLt0nE7PgwektkDg@mail.gmail.com>


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

      parent reply	other threads:[~2016-08-22 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  8:48 Emil Velikov
2016-08-22  8:58 ` Christian König
2016-08-22 10:28 ` Mikko Rapeli
2016-08-22 10:38 ` Rob Clark
2016-08-22 14:38   ` Daniel Vetter
2016-08-22 15:05     ` Emil Velikov
2016-08-22 15:40       ` Daniel Vetter
2016-08-22 21:12 ` randyf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.SOC.2.00.1608221348530.19914@sibernet.com \
    --to=randyf@sibernet.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikko.rapeli@iki.fi \
    --cc=robdclark@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®