From: David Miller <davem@davemloft.net>
To: himangi774@gmail.com
Cc: alex.bluesman.smirnov@gmail.com, dbaryshkov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, julia.lawall@lip6.fr
Subject: Re: [PATCH] ieee802154: Introduce the use of the managed version of kzalloc
Date: Sun, 18 May 2014 20:57:26 -0400 (EDT) [thread overview]
Message-ID: <20140518.205726.138371667211604965.davem@davemloft.net> (raw)
In-Reply-To: <20140516180935.GA13004@himangi-Dell>
From: Himangi Saraogi <himangi774@gmail.com>
Date: Fri, 16 May 2014 23:39:35 +0530
> This patch moves data allocated using kzalloc to managed data allocated
> using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> functions.
Likewise please add an explicit linux/device.h include to make sure
the devm_*() routine declarations are unambiguously available.
prev parent reply other threads:[~2014-05-19 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 18:09 [PATCH] ieee802154: Introduce the use of the managed version of kzalloc Himangi Saraogi
2014-05-19 0:57 ` David Miller [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=20140518.205726.138371667211604965.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=himangi774@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@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