From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
manuel.stahl@iis.fraunhofer.de,
Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 0/3] staging:iio: more buffer related cleanups.
Date: Sun, 27 Nov 2011 14:46:50 +0000 [thread overview]
Message-ID: <1322405213-13570-1-git-send-email-jic23@kernel.org> (raw)
These were after the inkern pull interface stuff in my tree, but
with a closer look they clearly aren't dependent on it so I'll tack
them on to the end of the previous series if everyone is happy.
Jonathan
Jonathan Cameron (3):
staging:iio:buffer scrap to_iio_buffer as it no longer has meaning.
staging:iio:buffer struct iio_buffer doesn't need an indio_dev
pointer.
staging:iio:buffer.h update struct buffer docs.
drivers/staging/iio/accel/sca3000_core.c | 6 +++---
drivers/staging/iio/accel/sca3000_ring.c | 11 ++++-------
drivers/staging/iio/buffer.h | 21 +++++++++++----------
drivers/staging/iio/gyro/adis16260_core.c | 15 ++++++++++-----
drivers/staging/iio/impedance-analyzer/ad5933.c | 4 ++--
drivers/staging/iio/industrialio-buffer.c | 15 +++++++--------
drivers/staging/iio/kfifo_buf.c | 2 +-
drivers/staging/iio/ring_sw.c | 2 +-
8 files changed, 39 insertions(+), 37 deletions(-)
--
1.7.7.3
next reply other threads:[~2011-11-27 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 14:46 Jonathan Cameron [this message]
2011-11-27 14:46 ` [PATCH 1/3] staging:iio:buffer scrap to_iio_buffer as it no longer has meaning Jonathan Cameron
2011-11-27 14:46 ` [PATCH 2/3] staging:iio:buffer struct iio_buffer doesn't need an indio_dev pointer Jonathan Cameron
2011-11-27 14:46 ` [PATCH 3/3] staging:iio:buffer.h update struct buffer docs 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=1322405213-13570-1-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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).