From: Lucas Stankus <lucas.p.stankus@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] staging: iio: cdc: ad7746: initial effort to move out of staging
Date: Sun, 23 May 2021 14:11:35 -0300 [thread overview]
Message-ID: <cover.1621786036.git.lucas.p.stankus@gmail.com> (raw)
Tidy up driver code by removing vague comments, simplifying probe
return, and extracting capdac register write to a separate function.
These small patches are a starting point for improving the ad7746 driver,
hopefully to a point where it's possible to get it out of staging. I'm
looking up to feedback on what could be improved to accomplish that.
changelog v1 -> v2:
- Dropped num_channels fixup patch (applied from previous series).
- Split general code style patch into several atomic ones.
- New patch to catch capdac write boilerplate into a single function.
Lucas Stankus (3):
staging: iio: cdc: ad7746: remove ordinary comments
staging: iio: cdc: ad7746: clean up probe return
staging: iio: cdc: ad7746: extract capac setup to own function
drivers/staging/iio/cdc/ad7746.c | 58 +++++++++++++-------------------
1 file changed, 23 insertions(+), 35 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-23 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 17:11 Lucas Stankus [this message]
2021-05-23 17:11 ` [PATCH v2 1/3] staging: iio: cdc: ad7746: remove ordinary comments Lucas Stankus
2021-05-23 17:12 ` [PATCH v2 2/3] staging: iio: cdc: ad7746: clean up probe return Lucas Stankus
2021-05-24 7:53 ` Alexandru Ardelean
2021-05-23 17:12 ` [PATCH v2 3/3] staging: iio: cdc: ad7746: extract capac setup to own function Lucas Stankus
2021-05-24 8:09 ` Alexandru Ardelean
2021-05-26 17:07 ` [PATCH v2 0/3] staging: iio: cdc: ad7746: initial effort to move out of staging Jonathan Cameron
2021-05-31 1:48 ` Lucas Stankus
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.1621786036.git.lucas.p.stankus@gmail.com \
--to=lucas.p.stankus@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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