From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: jic23@cam.ac.uk
Subject: + staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case.patch added to -mm tree
Date: Wed, 28 Jul 2010 16:18:29 -0700 [thread overview]
Message-ID: <201007282318.o6SNITPI008347@imap1.linux-foundation.org> (raw)
The patch titled
staging:iio:adis16350 add dummy ring functions for no ring build case
has been added to the -mm tree. Its filename is
staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: staging:iio:adis16350 add dummy ring functions for no ring build case
From: Jonathan Cameron <jic23@cam.ac.uk>
Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/staging/iio/imu/adis16350.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff -puN drivers/staging/iio/imu/adis16350.h~staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case drivers/staging/iio/imu/adis16350.h
--- a/drivers/staging/iio/imu/adis16350.h~staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case
+++ a/drivers/staging/iio/imu/adis16350.h
@@ -165,5 +165,13 @@ adis16350_read_data_from_ring(struct dev
return 0;
}
+int adis16350_configure_ring(struct iio_dev *indio_dev)
+{
+ return 0;
+}
+
+void adis16350_unconfigure_ring(struct iio_dev *indio_dev)
+{
+}
#endif /* CONFIG_IIO_RING_BUFFER */
#endif /* SPI_ADIS16350_H_ */
_
Patches currently in -mm which might be from jic23@cam.ac.uk are
linux-next.patch
staging-iio-iio_sw_ring_helper_state-add-dummy-case-for-no-buffer-builds.patch
staging-iio-lis3l02dq-add-a-thresh_timestamp-field-to-state-for-no-ring-case.patch
staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case.patch
misc-rohm-bh1780gli-ambient-light-sensor-driver.patch
drivers-misc-support-for-the-pressure-sensor-bmp085-from-bosch-sensortec.patch
drivers-misc-support-for-the-pressure-sensor-bmp085-from-bosch-sensortec-fix.patch
drivers-misc-support-for-the-pressure-sensor-bmp085-from-bosch-sensortec-update.patch
add-abi-documentation-for-the-bmp085-digital-pressure-sensor.patch
bmp085-add-interface-documentation-and-link-to-datasheet.patch
hmc6352-add-driver-for-the-hmc6352-compass.patch
hwmon-driver-for-smm665-six-channel-active-dc-output-controller-monitor.patch
hwmon-smm665-driver-documentation.patch
next reply other threads:[~2010-07-28 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 23:18 akpm [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-30 21:20 + staging-iio-adis16350-add-dummy-ring-functions-for-no-ring-build-case.patch added to -mm tree akpm
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=201007282318.o6SNITPI008347@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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