mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: Ken Phillis Jr <kphillisjr@gmail.com>
Cc: Rob Clark <robdclark@gmail.com>,
	Emil Velikov <emil.l.velikov@gmail.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "include/uapi/drm/amdgpu_drm.h: use __u32 and __u64 from <linux/types.h>"
Date: Sat, 20 Aug 2016 21:03:18 +0300	[thread overview]
Message-ID: <20160820180318.GF5399@lakka.kapsi.fi> (raw)
In-Reply-To: <CACiKS=SH-BL-nF+X33fCtpjCdHsqGea01nr2ix3yanz0nCLKjA@mail.gmail.com>

Cc'ing lkml.

On Fri, Aug 19, 2016 at 09:18:24PM -0500, Ken Phillis Jr wrote:
> On Fri, Aug 19, 2016 at 8:46 PM, Rob Clark <robdclark@gmail.com> wrote:
> 
> > perhaps, but if the target audience for driver specific APIs is
> > libdrm/mesa, which already uses stdint types, then I fail to see the
> > point..
> >
> > It is a bit difference scenario for some of the core kms ioctls which
> > are not driver specific..  but most of the driver specific gpu related
> > ioctls tend to be rather complex and not intended for use by something
> > other than libdrm/mesa.
> >
> > BR,
> > -R
> >
> 
> I personally do not see the reason to break user space API in the first
> place.
> I know for a fact that the include file ( linux/types.h ) mentioned by the
> patch
> supports C99 integer data types since Linux Kernel Version 2.2.0. This makes
> the patch that got reverted completely meaningless since the only reason to
> make this change in the first place would be if the developer intends on
> backporting the driver to kernels older than version 2.2.0.

In userspace linux/types.h does not provide these integer data types to avoid
conflict with libc ones.

Thus several uapi headers fail to compile in userspace. Fix is to either
include libc side stdint.h in userspace but that was rejected by kernel
developers including Linus who are in favor of kernel specific double
underscore types.

-Mikko

  parent reply	other threads:[~2016-08-20 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1471614628-11585-1-git-send-email-maraeo@gmail.com>
     [not found] ` <759ce38b-eb22-ee27-243b-f99891519cfb@vodafone.de>
2016-08-19 14:52   ` Mikko Rapeli
2016-08-19 15:22     ` Marek Olšák
2016-08-19 17:11       ` Daniel Vetter
2016-08-19 17:12         ` Daniel Vetter
2016-08-19 17:21           ` Marek Olšák
     [not found]   ` <CACvgo50WfCT9F_WdKQ6rv=oytCMjq3SErbF02pzfhHgjKWxv5g@mail.gmail.com>
2016-08-20 17:58     ` Mikko Rapeli
2016-08-20 22:31       ` Rob Clark
2016-08-21  9:03       ` Christian König
     [not found]     ` <CAF6AEGuUYyaCXqb_fvFScCCj9K7aYCW2yTyvwfL4PPEi3d=K7A@mail.gmail.com>
     [not found]       ` <CACiKS=QcwuozPDDawbKp+scwhM-udL9C=R065FDUDhrP5UBJqw@mail.gmail.com>
     [not found]         ` <CAF6AEGtwYwXQN89bb-BVPYa8_kH3QdcPWoD6-K1zhn1q7Gc03A@mail.gmail.com>
     [not found]           ` <CACiKS=SH-BL-nF+X33fCtpjCdHsqGea01nr2ix3yanz0nCLKjA@mail.gmail.com>
2016-08-20 18:03             ` Mikko Rapeli [this message]
     [not found]     ` <CAAxE2A7aKeJW1x4s5iHuQYGp3QKO-h_0yrPCRdQ0VyYvm4cQNw@mail.gmail.com>
2016-08-20 18:08       ` Mikko Rapeli
2016-08-20 18:28         ` Marek Olšák
2016-08-20 18:37           ` Marek Olšák

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=20160820180318.GF5399@lakka.kapsi.fi \
    --to=mikko.rapeli@iki.fi \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=kphillisjr@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®