From: Jonathan Cameron <jic23@kernel.org>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
Lars-Peter Clausen <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] iio: inkern: put the IIO device when it fails to allocate memory
Date: Sat, 22 Sep 2012 10:14:16 +0100 [thread overview]
Message-ID: <505D8168.8000003@kernel.org> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F41EF5397@DQHE02.ent.ti.com>
On 09/18/2012 05:55 AM, Kim, Milo wrote:
> The reference count of the IIO device is increased if the IIO map has
> matched consumer name.
> After then, it tries to allocate the iio_channel which is used by the consumer.
> If it fails to allocate memory, the reference count should be decreased.
>
> This patch enables restoring the reference count of the IIO device.
>
> Signed-off-by: Milo(Woogyom) Kim <milo.kim@ti.com>
Thanks add to togreg branch of iio.git
> ---
> drivers/iio/inkern.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c
> index 13748c0..aff034b 100644
> --- a/drivers/iio/inkern.c
> +++ b/drivers/iio/inkern.c
> @@ -132,7 +132,7 @@ struct iio_channel *iio_channel_get(const char *name, const char *channel_name)
>
> channel = kzalloc(sizeof(*channel), GFP_KERNEL);
> if (channel == NULL)
> - return ERR_PTR(-ENOMEM);
> + goto error_no_mem;
>
> channel->indio_dev = c->indio_dev;
>
> @@ -151,6 +151,9 @@ error_no_chan:
> iio_device_put(c->indio_dev);
> kfree(channel);
> return ERR_PTR(-EINVAL);
> +error_no_mem:
> + iio_device_put(c->indio_dev);
> + return ERR_PTR(-ENOMEM);
> }
> EXPORT_SYMBOL_GPL(iio_channel_get);
>
>
prev parent reply other threads:[~2012-09-22 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 4:55 [PATCH 1/2] iio: inkern: put the IIO device when it fails to allocate memory Kim, Milo
2012-09-22 9:14 ` 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=505D8168.8000003@kernel.org \
--to=jic23@kernel.org \
--cc=Milo.Kim@ti.com \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--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