From: Jonathan Cameron <jic23@cam.ac.uk>
To: linux-iio@vger.kernel.org
Cc: Michael.Hennerich@analog.com, Jonathan Cameron <jic23@cam.ac.uk>
Subject: [PATCH 4/8] ioctl region for IIO.
Date: Wed, 24 Aug 2011 17:34:10 +0100 [thread overview]
Message-ID: <1314203654-22377-5-git-send-email-jic23@cam.ac.uk> (raw)
In-Reply-To: <1314203654-22377-1-git-send-email-jic23@cam.ac.uk>
Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
---
Documentation/ioctl/ioctl-number.txt | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Documentation/ioctl/ioctl-number.txt b/Documentation/ioctl/ioctl-number.txt
index 845a191..9991b22 100644
--- a/Documentation/ioctl/ioctl-number.txt
+++ b/Documentation/ioctl/ioctl-number.txt
@@ -220,6 +220,7 @@ Code Seq#(hex) Include File Comments
'i' 00-3F linux/i2o-dev.h conflict!
'i' 0B-1F linux/ipmi.h conflict!
'i' 80-8F linux/i8k.h
+'i' 90-AF drivers/staging/iio/chrdev.h
'j' 00-3F linux/joystick.h
'k' 00-0F linux/spi/spidev.h conflict!
'k' 00-05 video/kyro.h conflict!
--
1.7.3.4
next prev parent reply other threads:[~2011-08-24 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 16:34 [PATCH 0/8 V2] staging:iio chrdev merge series Jonathan Cameron
2011-08-24 16:34 ` [PATCH 1/8] staging:iio:kfifo buffer - push structure definition down into implementation Jonathan Cameron
2011-08-24 16:34 ` [PATCH 2/8] staging:iio:chrdev.h rationalization Jonathan Cameron
2011-08-24 16:34 ` [PATCH 3/8] staging:iio: remove specific chrdev for event reading. Get fd from ioctl on buffer Jonathan Cameron
2011-08-24 16:34 ` Jonathan Cameron [this message]
2011-08-24 16:34 ` [PATCH 5/8] staging:iio: squash chrdev handler remains into users Jonathan Cameron
2011-08-24 16:34 ` [PATCH 6/8] staging:iio: push the main buffer chrdev down to the top level Jonathan Cameron
2011-08-24 16:34 ` [PATCH 7/8] staging:iio: remove now defunct header definitions and add some statics Jonathan Cameron
2011-08-24 16:34 ` [PATCH 8/8] staging:iio:Documentation sysfs-bus-iio update for chrdev merge 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=1314203654-22377-5-git-send-email-jic23@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.