linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 1/9] staging: iio: ad7192: Use devm_* APIs
Date: Sat, 07 Sep 2013 21:51:17 +0100	[thread overview]
Message-ID: <522B91C5.6000101@kernel.org> (raw)
In-Reply-To: <CAK9yfHy_NR=dMr2j2wPVks3PX79U04J5eBSmkOku+949sZZm4g@mail.gmail.com>

On 09/01/13 06:51, Sachin Kamat wrote:
> On 1 September 2013 00:01, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 08/31/13 18:12, Sachin Kamat wrote:
>>> devm_* APIs are device managed and make code simpler.
>>>
>>> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
>>> ---
>>> This series is compile tested and based on togreg branch
>>> of iio tree.
>>
>> Just to note, there is a memory leak fixed by this patch as well
>> as the remove function didn't free the struct iio_dev before.
> 
> Yes. I forgot to mention that in the commit log. Thanks for noticing.
> 
>>
>> Thanks for these Sachin.  All look good to me.
>> I won't take them today as effectively IIO for 3.12 is now
>> closed, as I doubt we'll see more than one more rc on
>> 3.11, and others may want to have time to look through these.
> 
> I wasn't aware of it, sorry.
> 
>>
>> I'll pick them up in a few days and queue up for 3.13 assuming
>> no one spots anything I have missed.
> 
> Sure. Thanks.

All applied to the togreg branch of iio.git.

Thanks as ever for your work on these!

Jonathan

      reply	other threads:[~2013-09-07 19:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 17:12 [PATCH 1/9] staging: iio: ad7192: Use devm_* APIs Sachin Kamat
2013-08-31 17:12 ` [PATCH 2/9] staging: iio: ad7280a: Use devm_iio_device_alloc Sachin Kamat
2013-08-31 17:12 ` [PATCH 3/9] staging: iio: ad7291: Use devm_* APIs Sachin Kamat
2013-08-31 17:12 ` [PATCH 4/9] staging: iio: ad7606_core: " Sachin Kamat
2013-08-31 17:12 ` [PATCH 5/9] staging: iio: ad7780: " Sachin Kamat
2013-08-31 17:12 ` [PATCH 6/9] staging: iio: ad7816: " Sachin Kamat
2013-08-31 17:12 ` [PATCH 7/9] staging: iio: ad799x_core: " Sachin Kamat
2013-08-31 17:12 ` [PATCH 8/9] staging: iio: lpc32xx_adc: " Sachin Kamat
2013-08-31 17:12 ` [PATCH 9/9] staging: iio: adt7316: " Sachin Kamat
2013-08-31 18:31 ` [PATCH 1/9] staging: iio: ad7192: " Jonathan Cameron
2013-09-01  5:51   ` Sachin Kamat
2013-09-07 20:51     ` 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=522B91C5.6000101@kernel.org \
    --to=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=sachin.kamat@linaro.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).