From: Jonathan Cameron <jic23@cam.ac.uk>
To: linux-iio@vger.kernel.org
Cc: lars@metafoo.de
Subject: [PATCH 2/2] staging:iio: Use userspace types for iio_event_data
Date: Fri, 21 Oct 2011 12:49:38 +0100 [thread overview]
Message-ID: <1319197778-32347-3-git-send-email-jic23@cam.ac.uk> (raw)
In-Reply-To: <1319197778-32347-1-git-send-email-jic23@cam.ac.uk>
From: Lars-Peter Clausen <lars@metafoo.de>
Since we want to export struct iio_event_data to userspace use the userspace
integer types. Also add a include to linux/types.h.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
drivers/staging/iio/events.h | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/events.h b/drivers/staging/iio/events.h
index 08cf3d1..389c781 100644
--- a/drivers/staging/iio/events.h
+++ b/drivers/staging/iio/events.h
@@ -10,6 +10,7 @@
#define _IIO_EVENTS_H_
#include <linux/ioctl.h>
+#include <linux/types.h>
#include "types.h"
/**
@@ -19,8 +20,8 @@
* the interrupt handler)
*/
struct iio_event_data {
- u64 id;
- s64 timestamp;
+ __u64 id;
+ __s64 timestamp;
};
#define IIO_GET_EVENT_FD_IOCTL _IOR('i', 0x90, int)
--
1.7.7
next prev parent reply other threads:[~2011-10-21 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 11:49 [V2 PATCH 0/2] staging:iio: header reorganization Jonathan Cameron
2011-10-21 11:49 ` [PATCH 1/2] " Jonathan Cameron
2011-10-21 11:49 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-21 10:42 [PATCH] " Lars-Peter Clausen
2011-10-21 10:59 ` [PATCH 1/2] staging:iio: Add missing ioctl.h include to events.h Lars-Peter Clausen
2011-10-21 10:59 ` [PATCH 2/2] staging:iio: Use userspace types for iio_event_data Lars-Peter Clausen
2011-10-21 11:39 ` Jonathan Cameron
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=1319197778-32347-3-git-send-email-jic23@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@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).