From: Shreeya Patel <shreeya.patel23498@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, jeremyfertic@gmail.com,
shreeya.patel23498@gmail.com
Subject: [PATCH v4 0/3] adt7316 regmap implementation
Date: Sat, 26 Jan 2019 23:03:59 +0530 [thread overview]
Message-ID: <20190126173402.12428-1-shreeya.patel23498@gmail.com> (raw)
This patchset consist of some initial patches for heading
towards the regmap implementation and also the final patch
which enables the driver to use regmap API thus removing
the redundant and common code.
Changes in v4
-Rebase against iio's testing branch. Previous series
was rebased against greg's testing branch.
Changes in v3
-Fetch the changes from remote and rebase to have it in
the current working directory.
Changes in v2
-Change the val_bits to 8 and add two more patches
having a different change before the final implemetation
of regmap.
Shreeya Patel (3):
Staging: iio: adt7316: Remove irq from bus structure
Staging: iio: adt7316: Remove multi read and write functions
Staging: iio: adt7316: Add regmap support
drivers/staging/iio/addac/adt7316-i2c.c | 97 ++-------------
drivers/staging/iio/addac/adt7316-spi.c | 95 +++------------
drivers/staging/iio/addac/adt7316.c | 149 ++++++++++++------------
drivers/staging/iio/addac/adt7316.h | 15 +--
4 files changed, 104 insertions(+), 252 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-26 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 17:33 Shreeya Patel [this message]
2019-01-26 17:34 ` [PATCH v4 1/3] Staging: iio: adt7316: Remove irq from bus structure Shreeya Patel
2019-01-26 17:34 ` [PATCH v4 2/3] Staging: iio: adt7316: Remove multi read and write functions Shreeya Patel
2019-01-26 17:34 ` [PATCH v4 3/3] Staging: iio: adt7316: Add regmap support Shreeya Patel
2019-01-26 21:34 ` 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=20190126173402.12428-1-shreeya.patel23498@gmail.com \
--to=shreeya.patel23498@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremyfertic@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).