From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, greg@kroah.com
Cc: lars@metafoo.de, Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 0/5] staging:iio: inkern pull interfaces for staging tree.
Date: Mon, 5 Dec 2011 21:55:59 +0000 [thread overview]
Message-ID: <1323122164-32314-1-git-send-email-jic23@kernel.org> (raw)
Hi Greg,
This set is a little bit of a novelty. It's actually a direct lift
of a series that has been proposed and reviewed against the
set of patches for the core of IIO outside of the staging
tree. We need it here in staging for two reasons.
1) To allow for drivers using this to exist in the staging tree
with all the stuff that is there but not yet ready to go out
of staging.
2) To allow development of the push in kernel interface stuff (triggered
capture) to procede. We have no where near enough of the core
ready to go out of staging yet to be able to do that work there.
Anyhow, very little review here because it was all in the other thread.
For reference:
https://lkml.org/lkml/2011/11/7/258
I haven't lifted the acks across because they were obviously not
able to consider any issues of interaction with the rest of IIO
given they were only looking at a subset. (Not that I think
there are any!).
Lars-Peter pointed out a silly mess up to do with two patches
getting weirdly split up so that is fixed here wrt to the version
I posted to linux-iio.
Thanks,
Jonathan
Jonathan Cameron (5):
staging:iio: core: add datasheet_name to chan_spec
staging:iio:adc:max1363 add datasheet_name entries.
staging:iio:core add in kernel interface mapping and getting IIO
channels.
staging;iio: move iio data return types into types.h for use by
inkern
staging:iio::hwmon interface client driver.
drivers/staging/Makefile | 2 +-
drivers/staging/iio/Kconfig | 8 +
drivers/staging/iio/Makefile | 4 +-
drivers/staging/iio/adc/max1363_core.c | 2 +
drivers/staging/iio/iio.h | 17 ++-
drivers/staging/iio/iio_hwmon.c | 225 ++++++++++++++++++++++++++
drivers/staging/iio/industrialio-core.c | 268 ++++++++++++++++++++++++++++++-
drivers/staging/iio/inkern.c | 21 +++
drivers/staging/iio/inkern.h | 86 ++++++++++
drivers/staging/iio/types.h | 4 +
10 files changed, 623 insertions(+), 14 deletions(-)
create mode 100644 drivers/staging/iio/iio_hwmon.c
create mode 100644 drivers/staging/iio/inkern.c
create mode 100644 drivers/staging/iio/inkern.h
--
1.7.7.4
next reply other threads:[~2011-12-05 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:55 Jonathan Cameron [this message]
2011-12-05 21:56 ` [PATCH 1/5] staging:iio: core: add datasheet_name to chan_spec Jonathan Cameron
2011-12-05 21:56 ` [PATCH 2/5] staging:iio:adc:max1363 add datasheet_name entries Jonathan Cameron
2011-12-05 21:56 ` [PATCH 3/5] staging:iio:core add in kernel interface mapping and getting IIO channels Jonathan Cameron
2011-12-08 19:40 ` Greg KH
2011-12-08 21:05 ` Jonathan Cameron
2011-12-10 17:08 ` Jonathan Cameron
2011-12-10 19:15 ` Greg KH
2011-12-16 8:50 ` archive
2011-12-16 16:24 ` Greg KH
2011-12-16 19:41 ` Jonathan Cameron
2011-12-16 22:23 ` Greg KH
2011-12-17 15:54 ` Jonathan Cameron
2011-12-22 17:41 ` Mark Brown
2011-12-05 21:56 ` [PATCH 4/5] staging:iio: move iio data return types into types.h for use by inkern Jonathan Cameron
2011-12-05 21:56 ` [PATCH 5/5] staging:iio::hwmon interface client driver 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=1323122164-32314-1-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=greg@kroah.com \
--cc=lars@metafoo.de \
--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).