All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/4] staging:iio: Add support for multiple buffers
Date: Sat, 09 Jun 2012 18:56:46 +0100	[thread overview]
Message-ID: <4FD38E5E.20005@kernel.org> (raw)
In-Reply-To: <4FD33871.6080107@metafoo.de>

On 06/09/2012 12:50 PM, Lars-Peter Clausen wrote:
> On 06/09/2012 02:17 PM, Jonathan Cameron wrote:
>>>> [...]
>>>> @@ -534,31 +453,186 @@ static int iio_compute_scan_bytes(struct ii=
o_dev *indio_dev, const long *mask,
>>>>  	return bytes;
>>>>  }
>>>> =20
>>>> -int iio_sw_buffer_preenable(struct iio_dev *indio_dev)
>>>> +int iio_update_buffers(struct iio_dev *indio_dev,
>>>> +		       struct iio_buffer *insert_buffer,
>>>> +		       struct iio_buffer *remove_buffer)
>>>>  {
>>>> -	struct iio_buffer *buffer =3D indio_dev->buffer;
>>>> -	dev_dbg(&indio_dev->dev, "%s\n", __func__);
>>>> +	int ret;
>>>
>>> drivers/iio/industrialio-buffer.c: In function =91iio_update_buffer=
s=92:
>>> drivers/iio/industrialio-buffer.c:460: warning: =91ret=92 may be us=
ed
>>> uninitialized in this function
>>>
>>> I think there a missing 'return 0', before the error handling. Righ=
t now the
>>> code always sets active_scan_mask to NULL.
>> The setting to NULL definitely isn't right, but we do still need to
>> free the compoundmask.  I'll fix that up.
>=20
> Only if compoundmask !=3D active_scan_mask
indeed.
> --
> 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


  reply	other threads:[~2012-06-09 16:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 19:36 [PATCH 0/4 V2] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-05-30 19:36 ` [PATCH 1/4] " Jonathan Cameron
2012-06-08 15:13   ` Lars-Peter Clausen
2012-06-09 12:17     ` Jonathan Cameron
2012-06-09 11:50       ` Lars-Peter Clausen
2012-06-09 17:56         ` Jonathan Cameron [this message]
2012-05-30 19:36 ` [PATCH 2/4] staging:iio:in kernel users: Add a data field for channel specific info Jonathan Cameron
2012-05-30 19:36 ` [PATCH 3/4] staging:iio: add a callback buffer for in kernel push interface Jonathan Cameron
2012-05-30 19:36 ` [PATCH 4/4] staging:iio: Proof of concept input driver Jonathan Cameron
2012-06-08 15:27   ` Lars-Peter Clausen
2012-06-09 17:56     ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2012-06-30 19:06 [PATCH 0/4 V3] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-06-30 19:06 ` [PATCH 1/4] " Jonathan Cameron
2012-10-13  9:24 [PATCH 0/4 V5] staging:iio: Add support for multiple buffers (testing required!) Jonathan Cameron
2012-10-13  9:24 ` [PATCH 1/4] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-10-17  8:37   ` Lars-Peter Clausen
2012-10-19 15:03     ` Jonathan Cameron
2012-10-31 10:30 [PATCH 0/4 V6] staging:iio: Add support for multiple buffers (testing required!) Jonathan Cameron
2012-10-31 10:30 ` [PATCH 1/4] staging:iio: Add support for multiple buffers 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=4FD38E5E.20005@kernel.org \
    --to=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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 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.