All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton@enomsg.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'David Woodhouse'" <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/14] power: 88pm860x_charger: drop kfree of devm_kzalloc'd data
Date: Sun, 31 Mar 2013 23:29:11 -0700	[thread overview]
Message-ID: <20130401062911.GC30190@lizard> (raw)
In-Reply-To: <007101ce1e21$f39efcc0$dadcf640$%han@samsung.com>

On Mon, Mar 11, 2013 at 03:30:40PM +0900, Jingoo Han wrote:
> The devm_kzalloc function allocates memory that is released
> automatically, when a driver detaches. Thus, there is no reason
> to explicitly call kfree in probe or remove functions.
> 
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---

1-14 applied, thanks!

Anton

      parent reply	other threads:[~2013-04-01  6:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11  6:30 [PATCH 01/14] power: 88pm860x_charger: drop kfree of devm_kzalloc'd data Jingoo Han
2013-03-11  6:31 ` [PATCH 02/14] power: max8925_power: use devm_kzalloc() Jingoo Han
2013-03-11  6:31 ` [PATCH 03/14] power: da9030_battery: " Jingoo Han
2013-03-11  6:32 ` [PATCH 04/14] power: da9052-battery: " Jingoo Han
2013-03-11  6:32 ` [PATCH 05/14] power: ds2760_battery: " Jingoo Han
2013-03-11  6:33 ` [PATCH 06/14] power: ds2780_battery: " Jingoo Han
2013-03-11  6:33 ` [PATCH 07/14] power: gpio-charger: " Jingoo Han
2013-03-11  6:34 ` [PATCH 08/14] power: isp1704_charger: " Jingoo Han
2013-03-11  6:34 ` [PATCH 09/14] power: max8903_charger: " Jingoo Han
2013-03-11  6:34 ` [PATCH 10/14] power: max8997_charger: " Jingoo Han
2013-03-11  6:35 ` [PATCH 11/14] power: max8998_charger: " Jingoo Han
2013-03-11  6:35 ` [PATCH 12/14] power: pcf50633-charger: " Jingoo Han
2013-03-11  6:35 ` [PATCH 13/14] power: rx51_battery: " Jingoo Han
2013-03-11  6:36 ` [PATCH 14/14] power: wm831x_backup: " Jingoo Han
2013-04-01  6:29 ` Anton Vorontsov [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=20130401062911.GC30190@lizard \
    --to=anton@enomsg.org \
    --cc=dwmw2@infradead.org \
    --cc=jg1.han@samsung.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.