From: Jonathan Cameron <jic23@cam.ac.uk>
To: Bryan Freed <bfreed@chromium.org>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, rklein@nvidia.com,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/3] staging:iio: Add an iio channel type string to support proximity sensors.
Date: Wed, 06 Jul 2011 20:45:48 +0100 [thread overview]
Message-ID: <4E14BB6C.9040804@cam.ac.uk> (raw)
In-Reply-To: <1309978586-10092-2-git-send-email-bfreed@chromium.org>
On 07/06/11 19:56, Bryan Freed wrote:
> Add "proximity" to the iio_chan_type_name_spec_shared string list to
> support proximity sensors.
> Now this list fully matches the declared iio_chan_type enums.
>
> Signed-off-by: Bryan Freed <bfreed@chromium.org>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> drivers/staging/iio/industrialio-core.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/staging/iio/industrialio-core.c b/drivers/staging/iio/industrialio-core.c
> index 4987bf4..ef9a11e 100644
> --- a/drivers/staging/iio/industrialio-core.c
> +++ b/drivers/staging/iio/industrialio-core.c
> @@ -53,6 +53,7 @@ static const char * const iio_chan_type_name_spec_shared[] = {
> [IIO_MAGN] = "magn",
> [IIO_LIGHT] = "illuminance",
> [IIO_INTENSITY] = "intensity",
> + [IIO_PROXIMITY] = "proximity",
> [IIO_TEMP] = "temp",
> [IIO_INCLI] = "incli",
> [IIO_ROT] = "rot",
next prev parent reply other threads:[~2011-07-06 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 18:56 [PATCH 1/3] staging:iio: Reorder channel type strings to match the iio.h enums Bryan Freed
2011-07-06 18:56 ` [PATCH 2/3] staging:iio: Add an iio channel type string to support proximity sensors Bryan Freed
2011-07-06 19:45 ` Jonathan Cameron [this message]
2011-07-06 18:56 ` [PATCH 3/3] staging:iio:light:isl29018: Convert some of the isl29018 driver to the new IIO_CHAN framework Bryan Freed
2011-07-06 18:59 ` Bryan Freed
2011-07-06 19:44 ` [PATCH 1/3] staging:iio: Reorder channel type strings to match the iio.h enums Jonathan Cameron
2011-07-06 23:27 ` Greg KH
2011-07-07 17:03 ` Bryan Freed
2011-07-07 17:14 ` Greg KH
2011-07-07 17:14 ` Greg KH
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=4E14BB6C.9040804@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=bfreed@chromium.org \
--cc=gregkh@suse.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rklein@nvidia.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.