From: Lars-Peter Clausen <lars@metafoo.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
Michael Hennerich <michael.hennerich@analog.com>,
linux-iio@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org, drivers@analog.com
Subject: Re: [PATCH 2/2] staging:iio:dac: Add AD5421 driver
Date: Wed, 26 Oct 2011 15:21:16 +0200 [thread overview]
Message-ID: <4EA8094C.7090708@metafoo.de> (raw)
In-Reply-To: <1319630467-6924-2-git-send-email-lars@metafoo.de>
On 10/26/2011 02:01 PM, Lars-Peter Clausen wrote:
> This patch adds support for the Analog Devices AD5421 Loop-Powered, 4mA to 20mA
> DAC.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> [...]
>
> drivers/staging/iio/events.h | 3 +-
>
> [...]
> diff --git a/drivers/staging/iio/events.h b/drivers/staging/iio/events.h
> index 7cf9306..2b4d2d9 100644
> --- a/drivers/staging/iio/events.h
> +++ b/drivers/staging/iio/events.h
> @@ -56,7 +56,8 @@ enum iio_event_direction {
> type, chan, chan1, chan2) \
> (((u64)type << 56) | ((u64)diff << 55) | \
> ((u64)direction << 48) | ((u64)modifier << 40) | \
> - ((u64)chan_type << 32) | (chan2 << 16) | chan1 | chan)
> + ((u64)chan_type << 32) | (((s16)chan2) << 16) | ((s16)chan1) | \
> + ((s16)chan))
>
Uhm, this was not supposed to be in this patch...
>
> #define IIO_EV_DIR_MAX 4
next prev parent reply other threads:[~2011-10-26 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 12:01 [PATCH 1/2] staging:iio: Make write_event_value callback optional Lars-Peter Clausen
2011-10-26 12:01 ` [PATCH 2/2] staging:iio:dac: Add AD5421 driver Lars-Peter Clausen
2011-10-26 13:21 ` Lars-Peter Clausen [this message]
2011-10-26 17:04 ` Jonathan Cameron
2011-10-27 7:25 ` Lars-Peter Clausen
2011-10-26 12:02 ` [PATCH 1/2] staging:iio: Make write_event_value callback optional 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=4EA8094C.7090708@metafoo.de \
--to=lars@metafoo.de \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=drivers@analog.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.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 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.