linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Laskar <gabriel@lse.epita.fr>
To: DRI devel <dri-devel@lists.freedesktop.org>
Cc: Gabriel Laskar <gabriel@lse.epita.fr>,
	David Airlie <airlied@linux.ie>,
	"open list:ABI/API" <linux-api@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/9] include/uapi/drm/armada_drm.h: use __u{32,64} types instead of uint{32,64}_t
Date: Thu, 12 Nov 2015 19:14:03 +0100	[thread overview]
Message-ID: <1447352051-22022-2-git-send-email-gabriel@lse.epita.fr> (raw)
In-Reply-To: <1447352051-22022-1-git-send-email-gabriel@lse.epita.fr>

Kernel headers should use linux/types.h

Signed-off-by: Gabriel Laskar <gabriel@lse.epita.fr>
---
 include/uapi/drm/armada_drm.h | 24 +++++++++++++-----------
 1 file changed, 13 insertions(+), 11 deletions(-)

diff --git a/include/uapi/drm/armada_drm.h b/include/uapi/drm/armada_drm.h
index 8dec3fd..77184b7 100644
--- a/include/uapi/drm/armada_drm.h
+++ b/include/uapi/drm/armada_drm.h
@@ -9,6 +9,8 @@
 #ifndef DRM_ARMADA_IOCTL_H
 #define DRM_ARMADA_IOCTL_H
 
+#include <linux/types.h>
+
 #define DRM_ARMADA_GEM_CREATE		0x00
 #define DRM_ARMADA_GEM_MMAP		0x02
 #define DRM_ARMADA_GEM_PWRITE		0x03
@@ -17,27 +19,27 @@
 	DRM_##dir(DRM_COMMAND_BASE + DRM_ARMADA_##name, struct drm_armada_##str)
 
 struct drm_armada_gem_create {
-	uint32_t handle;
-	uint32_t size;
+	__u32 handle;
+	__u32 size;
 };
 #define DRM_IOCTL_ARMADA_GEM_CREATE \
 	ARMADA_IOCTL(IOWR, GEM_CREATE, gem_create)
 
 struct drm_armada_gem_mmap {
-	uint32_t handle;
-	uint32_t pad;
-	uint64_t offset;
-	uint64_t size;
-	uint64_t addr;
+	__u32 handle;
+	__u32 pad;
+	__u64 offset;
+	__u64 size;
+	__u64 addr;
 };
 #define DRM_IOCTL_ARMADA_GEM_MMAP \
 	ARMADA_IOCTL(IOWR, GEM_MMAP, gem_mmap)
 
 struct drm_armada_gem_pwrite {
-	uint64_t ptr;
-	uint32_t handle;
-	uint32_t offset;
-	uint32_t size;
+	__u64 ptr;
+	__u32 handle;
+	__u32 offset;
+	__u32 size;
 };
 #define DRM_IOCTL_ARMADA_GEM_PWRITE \
 	ARMADA_IOCTL(IOW, GEM_PWRITE, gem_pwrite)
-- 
2.6.2

       reply	other threads:[~2015-11-12 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447352051-22022-1-git-send-email-gabriel@lse.epita.fr>
2015-11-12 18:14 ` Gabriel Laskar [this message]
2015-11-12 18:14 ` [PATCH 2/9] include/uapi/drm/virtgpu_drm.h: use __u{32,64} types instead of uint{32,64}_t Gabriel Laskar
2015-11-12 18:14 ` [PATCH 3/9] include/uapi/drm/qxl_drm.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 4/9] include/uapi/drm/nouveau_drm.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 5/9] include/uapi/drm/amdgpu_drm.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 6/9] include/uapi/drm/armada_drm.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 7/9] include/uapi/drm/drm_mode.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 8/9] include/uapi/drm/vmwgfx_drm.h: " Gabriel Laskar
2015-11-12 18:14 ` [PATCH 9/9] include/uapi/drm/omap_drm.h: " Gabriel Laskar

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=1447352051-22022-2-git-send-email-gabriel@lse.epita.fr \
    --to=gabriel@lse.epita.fr \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).