From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Barry Song <21cnbao@gmail.com>,
Vladimir Barinov <vbarinov@embeddedalley.com>,
Richard Purdie <richard@openedhand.com>
Subject: Re: [PATCH 0/5] ASoC: Fix incorrect kfree in error path
Date: Tue, 16 Nov 2010 09:52:45 +0000 [thread overview]
Message-ID: <1289901165.3338.12.camel@odin> (raw)
In-Reply-To: <1289894800.19543.2.camel@mola>
On Tue, 2010-11-16 at 16:06 +0800, Axel Lin wrote:
> This serial of patches fixes incorrect kfree in error path.
>
> Axel Lin (5):
> ASoC: Fix incorrect kfree in ad1836_probe error path
> ASoC: Fix incorrect kfree in ad193x_probe error path
> ASoC: Fix incorrect kfree in aic3x_probe error path
> ASoC: Fix incorrect kfree in wm8731_probe error path
> ASoC: Fix incorrect kfree in wm8962_probe error path
>
> sound/soc/codecs/ad1836.c | 1 -
> sound/soc/codecs/ad193x.c | 1 -
> sound/soc/codecs/tlv320aic3x.c | 1 -
> sound/soc/codecs/wm8731.c | 1 -
> sound/soc/codecs/wm8962.c | 1 -
> 5 files changed, 0 insertions(+), 5 deletions(-)
>
All
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-11-16 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 8:06 [PATCH 0/5] ASoC: Fix incorrect kfree in error path Axel Lin
2010-11-16 8:08 ` [PATCH 1/5] ASoC: Fix incorrect kfree in ad1836_probe " Axel Lin
2010-11-16 8:08 ` [PATCH 2/5] ASoC: Fix incorrect kfree in ad193x_probe " Axel Lin
2010-11-16 8:09 ` [PATCH 3/5] ASoC: Fix incorrect kfree in aic3x_probe " Axel Lin
2010-11-16 8:10 ` [PATCH 4/5] ASoC: Fix incorrect kfree in wm8731_probe " Axel Lin
2010-11-16 8:11 ` [PATCH 5/5] ASoC: Fix incorrect kfree in wm8962_probe " Axel Lin
2010-11-16 9:52 ` Liam Girdwood [this message]
2010-11-16 11:37 ` [PATCH 0/5] ASoC: Fix incorrect kfree in " Mark Brown
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=1289901165.3338.12.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=21cnbao@gmail.com \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@openedhand.com \
--cc=vbarinov@embeddedalley.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