From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: alan@signal11.us, Varka Bhadram <varkab@cdac.in>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-zigbee-devel@lists.sourceforge.net, alex.aing@gmail.com,
davem@davemloft.net
Subject: Re: [Linux-zigbee-devel] [PATCH net-next v2] mrf24j40: add managed API's provided by device layer
Date: Thu, 29 May 2014 10:50:02 +0200 [thread overview]
Message-ID: <20140529084959.GA26220@omega> (raw)
In-Reply-To: <1401343536-20361-1-git-send-email-varkab@cdac.in>
Hi Varka,
On Thu, May 29, 2014 at 11:35:35AM +0530, Varka Bhadram wrote:
> forgot to use devm_* for spi buff.
> sorry for that.
>
> -Varka Bhadram
>
> Signed-off-by: Varka Bhadram <varkab@cdac.in>
> ---
> drivers/net/ieee802154/mrf24j40.c | 21 +++++++++------------
> 1 file changed, 9 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/net/ieee802154/mrf24j40.c b/drivers/net/ieee802154/mrf24j40.c
> index 78a6552..90aed9b 100644
> --- a/drivers/net/ieee802154/mrf24j40.c
> +++ b/drivers/net/ieee802154/mrf24j40.c
> @@ -618,10 +618,10 @@ static int mrf24j40_probe(struct spi_device *spi)
>
> printk(KERN_INFO "mrf24j40: probe(). IRQ: %d\n", spi->irq);
>
> - devrec = kzalloc(sizeof(struct mrf24j40), GFP_KERNEL);
> + devrec = devm_kzalloc(&spi->dev, sizeof(struct mrf24j40), GFP_KERNEL);
> if (!devrec)
> goto err_devrec;
> - devrec->buf = kzalloc(3, GFP_KERNEL);
> + devrec->buf = devm_kzalloc(&spi->dev, 3, GFP_KERNEL);
> if (!devrec->buf)
> goto err_buf;
>
> @@ -676,12 +676,13 @@ static int mrf24j40_probe(struct spi_device *spi)
> val &= ~0x3; /* Clear RX mode (normal) */
> write_short_reg(devrec, REG_RXMCR, val);
>
> - ret = request_threaded_irq(spi->irq,
> - NULL,
> - mrf24j40_isr,
> - IRQF_TRIGGER_LOW|IRQF_ONESHOT,
> - dev_name(&spi->dev),
> - devrec);
> + ret = devm_request_threaded_irq(&spi->dev,
> + spi->irq,
> + NULL,
> + mrf24j40_isr,
> + IRQF_TRIGGER_LOW|IRQF_ONESHOT,
> + dev_name(&spi->dev),
> + devrec);
>
when using devm_* it's also freed when the probe function failed, so you
can also remove the error path handling.
err_alloc_dev:
kfree(devrec->buf);
err_buf:
kfree(devrec);
and so on...
- Alex
prev parent reply other threads:[~2014-05-29 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 6:05 [PATCH net-next v2] mrf24j40: add managed API's provided by device layer Varka Bhadram
2014-05-29 8:50 ` Alexander Aring [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=20140529084959.GA26220@omega \
--to=alex.aring@gmail.com \
--cc=alan@signal11.us \
--cc=alex.aing@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=varkab@cdac.in \
--cc=varkabhadram@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).