From: Lucas Stankus <lucas.p.stankus@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] iio: adc: ad7923: convert driver resources routines to device-managed counterparts
Date: Sun, 28 Mar 2021 18:45:39 -0300 [thread overview]
Message-ID: <cover.1616966903.git.lucas.p.stankus@gmail.com> (raw)
Following the initiative proposed by Alexandru, this patch series aims
to convert the ad7923 to use only device-managed routines.
Part of the driver was already using devm_ functions, so it was possible
to convert the remainder of it without much hassle.
With that, the deregistration function was no longer necessary and could
be entirely removed from the driver.
Lucas Stankus (3):
iio: adc: ad7923: use devm_add_action_or_reset for regulator disable
iio: adc: ad7923: use device-managed function for triggered buffer
iio: adc: ad7923: register device with devm_iio_device_register
drivers/iio/adc/ad7923.c | 39 +++++++++++++--------------------------
1 file changed, 13 insertions(+), 26 deletions(-)
--
2.31.0
next reply other threads:[~2021-03-28 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 21:45 Lucas Stankus [this message]
2021-03-28 21:46 ` [PATCH 1/3] iio: adc: ad7923: use devm_add_action_or_reset for regulator disable Lucas Stankus
2021-03-28 21:46 ` [PATCH 2/3] iio: adc: ad7923: use device-managed function for triggered buffer Lucas Stankus
2021-03-28 21:46 ` [PATCH 3/3] iio: adc: ad7923: register device with devm_iio_device_register Lucas Stankus
2021-03-29 7:06 ` Lars-Peter Clausen
2021-03-29 11:18 ` Jonathan Cameron
2021-03-29 7:18 ` [PATCH 0/3] iio: adc: ad7923: convert driver resources routines to device-managed counterparts Alexandru Ardelean
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=cover.1616966903.git.lucas.p.stankus@gmail.com \
--to=lucas.p.stankus@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.