From: Jonathan Cameron <jic23@cam.ac.uk>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example
Date: Fri, 15 Jun 2012 13:46:08 +0100 [thread overview]
Message-ID: <4FDB2E90.3090901@cam.ac.uk> (raw)
In-Reply-To: <1339714260-8361-4-git-send-email-pmeerw@pmeerw.net>
Fair enough though would be good to have a comment that says
what driver actually sends altvoltage events...
On 6/14/2012 11:50 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
> .../staging/iio/Documentation/iio_event_monitor.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/iio/Documentation/iio_event_monitor.c b/drivers/staging/iio/Documentation/iio_event_monitor.c
> index 2227584..4326e9e 100644
> --- a/drivers/staging/iio/Documentation/iio_event_monitor.c
> +++ b/drivers/staging/iio/Documentation/iio_event_monitor.c
> @@ -45,6 +45,7 @@ static const char * const iio_chan_type_name_spec[] = {
> [IIO_ANGL] = "angl",
> [IIO_TIMESTAMP] = "timestamp",
> [IIO_CAPACITANCE] = "capacitance",
> + [IIO_ALTVOLTAGE] = "altvoltage",
> };
>
> static const char * const iio_ev_type_text[] = {
> @@ -92,6 +93,7 @@ static bool event_is_known(struct iio_event_data *event)
> case IIO_ANGL:
> case IIO_TIMESTAMP:
> case IIO_CAPACITANCE:
> + case IIO_ALTVOLTAGE:
> break;
> default:
> return false;
next prev parent reply other threads:[~2012-06-15 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:50 [PATCH 1/6] iio: sysfs-bus-iio typo Peter Meerwald
2012-06-14 22:50 ` [PATCH 2/6] iio: cleanup sysfs-bus-iio-light-lm3533-als Peter Meerwald
2012-06-15 12:48 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 3/6] iio: iio/machine.h typo Peter Meerwald
2012-06-15 12:46 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example Peter Meerwald
2012-06-15 12:46 ` Jonathan Cameron [this message]
2012-06-14 22:50 ` [PATCH 5/6] iio staging: typos Peter Meerwald
2012-06-15 12:45 ` Jonathan Cameron
2012-06-14 22:51 ` [PATCH 6/6] iio: iio/events.h typos Peter Meerwald
2012-06-15 12:43 ` Jonathan Cameron
2012-06-15 12:48 ` [PATCH 1/6] iio: sysfs-bus-iio typo Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-06-15 17:25 Peter Meerwald
2012-06-15 17:25 ` [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example Peter Meerwald
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=4FDB2E90.3090901@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).