From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 1/5] staging:iio fill in some missing docs
Date: Sat, 3 Mar 2012 11:39:11 +0000 [thread overview]
Message-ID: <1330774755-18031-2-git-send-email-jic23@kernel.org> (raw)
In-Reply-To: <1330774755-18031-1-git-send-email-jic23@kernel.org>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
---
drivers/staging/iio/iio.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
index b9cd454..833a849 100644
--- a/drivers/staging/iio/iio.h
+++ b/drivers/staging/iio/iio.h
@@ -331,6 +331,8 @@ struct iio_buffer_setup_ops {
* @name: [DRIVER] name of the device.
* @info: [DRIVER] callbacks and constant info from driver
* @info_exist_lock: [INTERN] lock to prevent use during removal
+ * @setup_ops: [DRIVER] callbacks to call before and after buffer
+ * enable/disable
* @chrdev: [INTERN] associated character device
* @groups: [INTERN] attribute groups
* @groupcounter: [INTERN] index of next attribute group
--
1.7.9.2
next prev parent reply other threads:[~2012-03-03 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 11:39 [PATCH 0/5] IIO mixed bag of trivial + fixes Jonathan Cameron
2012-03-03 11:39 ` Jonathan Cameron [this message]
2012-03-03 11:39 ` [PATCH 2/5] staging:iio:accel:lis3l02dq add symmetry to check for presence of trigger Jonathan Cameron
2012-03-03 11:39 ` [PATCH 3/5] staging:iio: use spi->irq valid rather than querying available modes Jonathan Cameron
2012-03-03 11:39 ` [PATCH 4/5] staging:iio:adc:max1363 fix missing update_scan_mask callback Jonathan Cameron
2012-03-03 11:39 ` [PATCH 5/5] staging:iio:iio_core.h make less dependent on other included headers 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=1330774755-18031-2-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--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).