From: Jonathan Cameron <jic23@kernel.org>
To: Roland Stigge <stigge@antcom.de>
Cc: Peter Meerwald <pmeerw@pmeerw.net>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: remove indio_dev pointer from max517_data
Date: Thu, 07 Jun 2012 17:01:59 +0100 [thread overview]
Message-ID: <4FD0D077.7080803@kernel.org> (raw)
In-Reply-To: <4FD07F42.5060007@antcom.de>
On 06/07/2012 11:15 AM, Roland Stigge wrote:
> On 07/06/12 10:31, Peter Meerwald wrote:
>> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
>
Well that would explain where the other one came from ;)
> Acked-by: Roland Stigge <stigge@antcom.de>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
>> ---
>> drivers/iio/dac/max517.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/iio/dac/max517.c b/drivers/iio/dac/max517.c
>> index 92c77c8..352abe2 100644
>> --- a/drivers/iio/dac/max517.c
>> +++ b/drivers/iio/dac/max517.c
>> @@ -43,7 +43,6 @@ enum max517_device_ids {
>> };
>>
>> struct max517_data {
>> - struct iio_dev *indio_dev;
>> struct i2c_client *client;
>> unsigned short vref_mv[2];
>> };
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-07 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 8:31 [PATCH 1/2] iio: remove indio_dev pointer from max517_data Peter Meerwald
2012-06-07 8:31 ` [PATCH 2/2] iio: max517: mark probe() and remove() with __devinit and __devexit Peter Meerwald
2012-06-07 10:16 ` Roland Stigge
2012-06-07 16:01 ` Jonathan Cameron
2012-06-07 10:15 ` [PATCH 1/2] iio: remove indio_dev pointer from max517_data Roland Stigge
2012-06-07 16:01 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-08 6:54 Peter Meerwald
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=4FD0D077.7080803@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stigge@antcom.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.