From: alisadariana@gmail.com
To: unlisted-recipients:; (no To-header on input)
Cc: Alisa-Dariana Roman <alisa.roman@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Alexandru Tachici <alexandru.tachici@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] iio: adc: ad7192: Add improvements and feature
Date: Mon, 25 Sep 2023 00:51:45 +0300 [thread overview]
Message-ID: <20230924215148.102491-1-alisadariana@gmail.com> (raw)
From: Alisa-Dariana Roman <alisa.roman@analog.com>
Hello again,
Thank you Jonathan for the feedback! Here is the updated series of
patches for the ad7192 driver.
Quick reminder that the patches need to be applied in order.
v2 -> v3
- move comment line above
- correct FIELD_PREP to FIELD_GET where needed
- remove unnecessary !!
- "rms" -> "RMS"
Link: https://lore.kernel.org/all/20230920003342.118813-1-alisadariana@gmail.com/
v1 -> v2
- replace old macros with FIELD_PREP() in commit "Use bitfield
access macros"
- update the other commits accordingly
Link: https://lore.kernel.org/all/20230918214854.252781-1-alisadariana@gmail.com/
Kind regards,
Alisa-Dariana Roman (3):
iio: adc: ad7192: Use bitfield access macros
iio: adc: ad7192: Improve f_order computation
iio: adc: ad7192: Add fast settling support
.../ABI/testing/sysfs-bus-iio-adc-ad7192 | 18 ++
drivers/iio/adc/ad7192.c | 241 ++++++++++++++----
2 files changed, 206 insertions(+), 53 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-24 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 21:51 alisadariana [this message]
2023-09-24 21:51 ` [PATCH v3 1/3] iio: adc: ad7192: Use bitfield access macros alisadariana
2023-09-30 17:13 ` Jonathan Cameron
2023-09-24 21:51 ` [PATCH v3 2/3] iio: adc: ad7192: Improve f_order computation alisadariana
2023-09-30 17:25 ` Jonathan Cameron
2023-09-24 21:51 ` [PATCH v3 3/3] iio: adc: ad7192: Add fast settling support alisadariana
2023-09-30 17:31 ` 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=20230924215148.102491-1-alisadariana@gmail.com \
--to=alisadariana@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.tachici@analog.com \
--cc=alisa.roman@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 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).