From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH] regulator: ad5398 - fix a memory leak
Date: Wed, 1 Sep 2010 10:15:45 +0100 [thread overview]
Message-ID: <20100901091544.GB17032@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1283308158.23075.1.camel@mola>
On Wed, Sep 01, 2010 at 10:29:18AM +0800, Axel Lin wrote:
> In current implementation, the address return from regulator_register()
> is different from the address for regulator_unregister().
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-09-01 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 2:29 [PATCH] regulator: ad5398 - fix a memory leak Axel Lin
2010-09-01 2:56 ` Zhang, Sonic
2010-09-01 9:15 ` Mark Brown [this message]
2010-09-01 11:54 ` Liam Girdwood
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=20100901091544.GB17032@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sonic.zhang@analog.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 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.