From: Tushar Behera <trblinux@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: alan@signal11.us, alex.bluesman.smirnov@gmail.com,
dbaryshkov@gmail.com, linux-zigbee-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, alex.aing@gmail.com,
Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH net-next v1] mrf24j40: add managed API's provided by device layer
Date: Thu, 29 May 2014 12:02:37 +0530 [thread overview]
Message-ID: <20140529063236.GA9679@linaro.org> (raw)
In-Reply-To: <1401338421-15394-1-git-send-email-varkab@cdac.in>
On Thu, May 29, 2014 at 10:10:21AM +0530, Varka Bhadram wrote:
> Hi,
> Previous patch having bug in using managed API's. I fixed that.
>
> Regards,
> Varka Bhadram.
Only add relevant commit message here, no need to add 'Hi' and
'Regards'.
Something like ...
"Added devres managed APIs"
>
> 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..f701cdb 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 = kzalloc(&spi->dev, 3, GFP_KERNEL);
devm_kzalloc()
Without this, it should not build at all. So remember to compile test
before sending the patches.
--
Warm regards,
Tushar
next prev parent reply other threads:[~2014-05-29 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 4:40 [PATCH net-next v1] mrf24j40: add managed API's provided by device layer Varka Bhadram
2014-05-29 6:32 ` Tushar Behera [this message]
2014-05-29 7:12 ` Varka Bhadram
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=20140529063236.GA9679@linaro.org \
--to=trblinux@gmail.com \
--cc=alan@signal11.us \
--cc=alex.aing@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=davem@davemloft.net \
--cc=dbaryshkov@gmail.com \
--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