From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 14/14] staging:iio:core drop the IIO_CHAN macro for ease of maintenance.
Date: Fri, 13 Apr 2012 10:43:00 +0100 [thread overview]
Message-ID: <1334310180-22170-15-git-send-email-jic23@kernel.org> (raw)
In-Reply-To: <1334310180-22170-1-git-send-email-jic23@kernel.org>
I was warned long ago that this macro would cause trouble but didn't
heed the advice, hence I'm unwinding it now!
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
---
drivers/staging/iio/iio.h | 17 -----------------
1 files changed, 0 insertions(+), 17 deletions(-)
diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
index 4824812..fa6fca0 100644
--- a/drivers/staging/iio/iio.h
+++ b/drivers/staging/iio/iio.h
@@ -176,23 +176,6 @@ struct iio_chan_spec {
#define IIO_ST(si, rb, sb, sh) \
{ .sign = si, .realbits = rb, .storagebits = sb, .shift = sh }
-/* Macro assumes input channels */
-#define IIO_CHAN(_type, _mod, _indexed, _proc, _name, _chan, _chan2, \
- _inf_mask, _address, _si, _stype, _event_mask) \
- { .type = _type, \
- .output = 0, \
- .modified = _mod, \
- .indexed = _indexed, \
- .processed_val = _proc, \
- .extend_name = _name, \
- .channel = _chan, \
- .channel2 = _chan2, \
- .info_mask = _inf_mask, \
- .address = _address, \
- .scan_index = _si, \
- .scan_type = _stype, \
- .event_mask = _event_mask }
-
#define IIO_CHAN_SOFT_TIMESTAMP(_si) \
{ .type = IIO_TIMESTAMP, .channel = -1, \
.scan_index = _si, .scan_type = IIO_ST('s', 64, 64, 0) }
--
1.7.0.4
next prev parent reply other threads:[~2012-04-13 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 9:42 [PATCH 00/14 V2] IIO: Kill off IIO_CHAN macro Jonathan Cameron
2012-04-13 9:42 ` [PATCH 01/14] staging:iio:accel:adis16201 unwind use of " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 02/14] staging:iio:accel:adis16203 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 03/14] staging:iio:accel:adis16204 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 04/14] staging:iio:accel:adis16209 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 05/14] staging:iio:accel:adis16240 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 06/14] staging:iio:accel:lis3l02dq " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 07/14] staging:iio:accel:sca3000 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 08/14] staging:iio:adc:ad7298 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 09/14] staging:iio:adc:ad7476 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 10/14] staging:iio:accel:ad7780 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 11/14] staging:iio:gyro:adis16260 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 12/14] staging:iio:impedance-analyzer:ad5933 " Jonathan Cameron
2012-04-13 9:42 ` [PATCH 13/14] staging:iio:meter:ade7758 " Jonathan Cameron
2012-04-13 9:43 ` Jonathan Cameron [this message]
2012-04-13 9:47 ` [PATCH 00/14 V2] IIO: Kill off " Jonathan Cameron
2012-04-13 9:56 ` Lars-Peter Clausen
2012-04-13 18:13 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 20:21 [PATCH 00/14] " Jonathan Cameron
2012-04-10 20:21 ` [PATCH 14/14] staging:iio:core drop the IIO_CHAN macro for ease of maintenance 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=1334310180-22170-15-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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).