From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Tachici <alexandru.tachici@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5 V2] iio: adc: ad7192: move out of staging
Date: Thu, 6 Feb 2020 09:47:56 +0000 [thread overview]
Message-ID: <20200206094756.52fe8bc0@archlinux> (raw)
In-Reply-To: <20200205171511.25912-1-alexandru.tachici@analog.com>
On Wed, 5 Feb 2020 19:15:06 +0200
Alexandru Tachici <alexandru.tachici@analog.com> wrote:
> This series of patches aim to move the ad7192 ADC from staging
> into mainline.
>
> 1. Makes probe fail in case get_voltage returns an error.
>
> 2. Changed the iio_chan_spec talbes in order to set the required
> attributes at compile time.
tables
>
> 3. Removed spi_device_id table and moved ID_* in of_Device_id table.
>
> 4. Updates inline sysfs docs.
>
> 5. Full-diff patch to move the ad7192 out of staging.
Couple of process things. Seems you have this thread with an
in reply to set to a different thread.
1) Obviously helps if it's the right thread ;)
2) Don't do it anyway. Threads get very deep if we take a few versions
for a driver so much better to just rely on naming and start a new
thread for each version.
Jonathan
>
> Alexandru Tachici (5):
> staging: iio: adc: ad7192: fail probe on get_voltage
> staging: iio: adc: ad7192: modify iio_chan_spec array
> staging: iio: adc: ad7192: removed spi_device_id
> Documentation: ABI: testing: ad7192: update sysfs docs
> staging: iio: adc: ad7192: move out of staging
>
> .../ABI/testing/sysfs-bus-iio-adc-ad7192 | 17 +-
> MAINTAINERS | 8 +
> drivers/iio/adc/Kconfig | 12 +
> drivers/iio/adc/Makefile | 1 +
> drivers/iio/adc/ad7192.c | 1043 +++++++++++++++++
> .../iio/Documentation/sysfs-bus-iio-ad7192 | 20 -
> drivers/staging/iio/adc/Kconfig | 12 -
> drivers/staging/iio/adc/Makefile | 1 -
> drivers/staging/iio/adc/ad7192.c | 1022 ----------------
> 9 files changed, 1075 insertions(+), 1061 deletions(-)
> create mode 100644 drivers/iio/adc/ad7192.c
> delete mode 100644 drivers/staging/iio/Documentation/sysfs-bus-iio-ad7192
> delete mode 100644 drivers/staging/iio/adc/ad7192.c
>
prev parent reply other threads:[~2020-02-06 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 8:54 [PATCH] iio: adc: ad7124: add 3db filter Alexandru Tachici
2020-02-02 16:22 ` Jonathan Cameron
2020-02-05 17:15 ` [PATCH 0/5 V2] iio: adc: ad7192: move out of staging Alexandru Tachici
2020-02-05 17:15 ` [PATCH 1/5 V2] staging: iio: adc: ad7192: fail probe on get_voltage Alexandru Tachici
2020-02-06 9:56 ` Jonathan Cameron
2020-02-05 17:15 ` [PATCH 2/5 V2] staging: iio: adc: ad7192: modify iio_chan_spec array Alexandru Tachici
2020-02-06 10:01 ` Jonathan Cameron
2020-02-05 17:15 ` [PATCH 3/5 V2] staging: iio: adc: ad7192: removed spi_device_id Alexandru Tachici
2020-02-06 10:03 ` Jonathan Cameron
2020-02-05 17:15 ` [PATCH 4/5 V2] Documentation: ABI: testing: ad7192: update sysfs docs Alexandru Tachici
2020-02-06 10:05 ` Jonathan Cameron
2020-02-05 17:15 ` [PATCH 5/5 V2] staging: iio: adc: ad7192: move out of staging Alexandru Tachici
2020-02-06 10:10 ` Jonathan Cameron
2020-02-06 10:20 ` Jonathan Cameron
2020-02-10 6:43 ` Ardelean, Alexandru
2020-02-14 13:03 ` Jonathan Cameron
2020-02-06 9:47 ` Jonathan Cameron [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=20200206094756.52fe8bc0@archlinux \
--to=jic23@kernel.org \
--cc=alexandru.tachici@analog.com \
--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).