From: Marek Vasut <marex@denx.de>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
linux-kernel@vger.kernel.org
Cc: lee.jones@linaro.org, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
harald@ccbib.org, stefan.wahren@i2se.com,
fabio.estevam@freescale.com
Subject: Re: [PATCH v11 0/5] mxs-lradc: Split driver into MFD
Date: Fri, 9 Dec 2016 00:02:04 +0100 [thread overview]
Message-ID: <51d581e9-a99a-cec4-efe9-3e5c896780da@denx.de> (raw)
In-Reply-To: <cover.1481234322.git.ksenija.stanojevic@gmail.com>
On 12/08/2016 11:27 PM, Ksenija Stanojevic wrote:
> Split existing driver mxs-lradc into MFD with touchscreen and
> IIO part.
>
> Tested on I.MX28
>
> Ksenija Stanojevic (5):
> mfd: mxs-lradc: Add support for mxs-lradc MFD
> iio: adc: mxs-lradc: Add support for adc driver
> input: touchscreen: mxs-lradc: Add support for touchscreen
> iio: adc: mxs-lradc: Remove driver
> mfd: Move binding document
>
> .../bindings/{iio/adc => mfd}/mxs-lradc.txt | 0
> drivers/iio/adc/Kconfig | 27 +-
> drivers/iio/adc/Makefile | 2 +-
> drivers/iio/adc/mxs-lradc-adc.c | 843 ++++++++++
> drivers/iio/adc/mxs-lradc.c | 1750 --------------------
> drivers/input/touchscreen/Kconfig | 10 +
> drivers/input/touchscreen/Makefile | 1 +
> drivers/input/touchscreen/mxs-lradc-ts.c | 739 +++++++++
> drivers/mfd/Kconfig | 17 +
> drivers/mfd/Makefile | 1 +
> drivers/mfd/mxs-lradc.c | 264 +++
> include/linux/mfd/mxs-lradc.h | 187 +++
> 12 files changed, 2076 insertions(+), 1765 deletions(-)
> rename Documentation/devicetree/bindings/{iio/adc => mfd}/mxs-lradc.txt (100%)
> create mode 100644 drivers/iio/adc/mxs-lradc-adc.c
> delete mode 100644 drivers/iio/adc/mxs-lradc.c
> create mode 100644 drivers/input/touchscreen/mxs-lradc-ts.c
> create mode 100644 drivers/mfd/mxs-lradc.c
> create mode 100644 include/linux/mfd/mxs-lradc.h
>
Except minor nit in 1/5, the whole series is:
Reviewed-by: Marek Vasut <marex@denx.de>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-12-08 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 22:27 [PATCH v11 0/5] mxs-lradc: Split driver into MFD Ksenija Stanojevic
2016-12-08 22:27 ` [PATCH v11 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD Ksenija Stanojevic
2016-12-08 22:56 ` Marek Vasut
2017-01-04 10:33 ` Lee Jones
2016-12-08 22:27 ` [PATCH v11 2/5] iio: adc: mxs-lradc: Add support for adc driver Ksenija Stanojevic
2016-12-08 22:27 ` [PATCH v11 3/5] input: touchscreen: mxs-lradc: Add support for touchscreen Ksenija Stanojevic
2016-12-27 22:39 ` Dmitry Torokhov
2017-01-20 12:25 ` Stefan Wahren
2017-01-21 20:57 ` Ksenija Stanojević
2017-01-23 10:53 ` Ksenija Stanojević
2016-12-08 22:27 ` [PATCH v11 4/5] iio: adc: mxs-lradc: Remove driver Ksenija Stanojevic
2016-12-08 22:27 ` [PATCH v11 5/5] mfd: Move binding document Ksenija Stanojevic
2017-01-04 10:57 ` Lee Jones
2016-12-08 23:02 ` Marek Vasut [this message]
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=51d581e9-a99a-cec4-efe9-3e5c896780da@denx.de \
--to=marex@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=harald@ccbib.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=ksenija.stanojevic@gmail.com \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.wahren@i2se.com \
/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).