From: "Nuno Sá" <nuno.sa@analog.com>
To: <linux-iio@vger.kernel.org>, <devel@driverdev.osuosl.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
"Hartmut Knaack" <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"Dragos Bogdan" <dragos.bogdan@analog.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: [PATCH v2 00/10] Use ADIS devm functions for trigger/buffer setup
Date: Tue, 15 Sep 2020 14:02:48 +0200 [thread overview]
Message-ID: <20200915120258.161587-1-nuno.sa@analog.com> (raw)
This series updates all users of `adis_setup_buffer_and_trigger()` to
use the devm version of it. The ultimate goal of the series is to drop
it from the lib as stated by Jonathan in [1].
[1]: https://marc.info/?l=linux-iio&m=158326796924980&w=2
Nuno Sá (10):
iio: adis16201: Use Managed device functions
iio: adis16209: Use Managed device functions
iio: adis16136: Use Managed device functions
iio: adis16260: Use Managed device functions
iio: adis16400: Use Managed device functions
iio: adis16460: Use Managed device functions
iio: adis16480: Use Managed device functions
staging: iio: adis16203: Use Managed device functions
staging: iio: adis16240: Use Managed device functions
iio: adis: Drop non Managed device functions
drivers/iio/accel/adis16201.c | 26 ++---------
drivers/iio/accel/adis16209.c | 25 ++---------
drivers/iio/gyro/adis16136.c | 37 ++++++----------
drivers/iio/gyro/adis16260.c | 33 +++++---------
drivers/iio/imu/adis16400.c | 38 +++++++---------
drivers/iio/imu/adis16460.c | 25 ++---------
drivers/iio/imu/adis16480.c | 55 +++++++++++------------
drivers/iio/imu/adis_buffer.c | 64 ++-------------------------
drivers/iio/imu/adis_trigger.c | 60 -------------------------
drivers/staging/iio/accel/adis16203.c | 26 ++---------
drivers/staging/iio/accel/adis16240.c | 25 ++---------
include/linux/iio/imu/adis.h | 27 -----------
12 files changed, 84 insertions(+), 357 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-15 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 12:02 Nuno Sá [this message]
2020-09-15 12:02 ` [PATCH v2 01/10] iio: adis16201: Use Managed device functions Nuno Sá
2020-09-15 12:02 ` [PATCH v2 02/10] iio: adis16209: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 03/10] iio: adis16136: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 04/10] iio: adis16260: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 05/10] iio: adis16400: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 06/10] iio: adis16460: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 07/10] iio: adis16480: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 08/10] staging: iio: adis16203: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 09/10] staging: iio: adis16240: " Nuno Sá
2020-09-15 12:02 ` [PATCH v2 10/10] iio: adis: Drop non " Nuno Sá
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=20200915120258.161587-1-nuno.sa@analog.com \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=dragos.bogdan@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).