From: Jonathan Cameron <jic23@kernel.org>
To: Zubair Lutfullah <zubair.lutfullah@gmail.com>
Cc: jic23@cam.ac.uk, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 2/3] iio: ti_am335x_adc: cleanup trigger related code
Date: Sun, 22 Sep 2013 20:20:57 +0100 [thread overview]
Message-ID: <523F4319.4010208@kernel.org> (raw)
In-Reply-To: <1379838005-15158-3-git-send-email-zubair.lutfullah@gmail.com>
On 09/22/13 09:20, Zubair Lutfullah wrote:
> Trigger related headers and variables are not needed
> as driver is now based on INDIO_BUFFER_HARDWARE mode
>
> Signed-off-by: Zubair Lutfullah <zubair.lutfullah@gmail.com>
Applied
> ---
> drivers/iio/adc/ti_am335x_adc.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
> index 91dce1f..4eb63eb 100644
> --- a/drivers/iio/adc/ti_am335x_adc.c
> +++ b/drivers/iio/adc/ti_am335x_adc.c
> @@ -30,9 +30,6 @@
> #include <linux/mfd/ti_am335x_tscadc.h>
> #include <linux/iio/buffer.h>
> #include <linux/iio/kfifo_buf.h>
> -#include <linux/iio/trigger.h>
> -#include <linux/iio/trigger_consumer.h>
> -#include <linux/iio/triggered_buffer.h>
>
> struct tiadc_device {
> struct ti_tscadc_dev *mfd_tscadc;
> @@ -40,7 +37,6 @@ struct tiadc_device {
> u8 channel_line[8];
> u8 channel_step[8];
> int buffer_en_ch_steps;
> - struct iio_trigger *trig;
> u16 data[8];
> };
>
>
next prev parent reply other threads:[~2013-09-22 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 8:20 [PATCH 0/3] iio: ti_am335x_adc: small fix and cleanup Zubair Lutfullah
2013-09-22 8:20 ` [PATCH 1/3] iio: ti_am335x_adc: fix static in function header Zubair Lutfullah
2013-09-22 18:03 ` Jonathan Cameron
2013-09-26 8:09 ` Zubair Lutfullah :
2013-09-22 8:20 ` [PATCH 2/3] iio: ti_am335x_adc: cleanup trigger related code Zubair Lutfullah
2013-09-22 19:20 ` Jonathan Cameron [this message]
2013-09-22 8:20 ` [PATCH 3/3] iio: ti_am335x_adc: cleanup error case Zubair Lutfullah
2013-09-22 19:21 ` 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=523F4319.4010208@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zubair.lutfullah@gmail.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).