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>
Subject: Re: [PATCH] ASoC: pxa-ssp: fix a memory leak in pxa_ssp_remove()
Date: Thu, 26 Aug 2010 09:47:08 +0100 [thread overview]
Message-ID: <20100826084708.GA26944@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTinTiOmGo4fpHnOdVPSTH1DuWQeLVvh1ysmwhVM0@mail.gmail.com>
On Thu, Aug 26, 2010 at 02:10:06PM +0800, Axel Lin wrote:
> I just thought this fix should be applied to 2.6.36.
> And ASoC tree will have this fix after merge 2.6.36.
It's a memory leak on unload for a driver for a device integrated into
an embedded SoC - I'd be astonished if anyone managed to run into it in
production.
prev parent reply other threads:[~2010-08-26 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 8:59 [PATCH] ASoC: pxa-ssp: fix a memory leak in pxa_ssp_remove() Axel Lin
2010-08-25 9:53 ` Liam Girdwood
2010-08-25 13:22 ` Mark Brown
2010-08-26 6:10 ` Axel Lin
2010-08-26 8:47 ` Mark Brown [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=20100826084708.GA26944@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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