From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: alsa-devel@alsa-project.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Jaswinder Singh Brar <jassi.brar@samsung.com>,
Sergey Lapin <slapin@ossfans.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Sedji Gaouaou <sedji.gaouaou@atmel.com>,
Mika Westerberg <mika.westerberg@iki.fi>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/8] ASoC: fix resource leak in error paths
Date: Thu, 25 Nov 2010 11:14:45 +0000 [thread overview]
Message-ID: <20101125111444.GD22298@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1290668785.30158.7.camel@mola>
On Thu, Nov 25, 2010 at 03:06:25PM +0800, Axel Lin wrote:
> This serial of patches fix resource leak in error paths.
All applied, thanks - thanks for taking the time to do so many cleanups
recently, it's appreciated.
WARNING: multiple messages have this Message-ID (diff)
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>,
alsa-devel@alsa-project.org, Jon Smirl <jonsmirl@gmail.com>,
Sergey Lapin <slapin@ossfans.org>,
Sedji Gaouaou <sedji.gaouaou@atmel.com>,
Jaswinder Singh Brar <jassi.brar@samsung.com>,
Mika Westerberg <mika.westerberg@iki.fi>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/8] ASoC: fix resource leak in error paths
Date: Thu, 25 Nov 2010 11:14:45 +0000 [thread overview]
Message-ID: <20101125111444.GD22298@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1290668785.30158.7.camel@mola>
On Thu, Nov 25, 2010 at 03:06:25PM +0800, Axel Lin wrote:
> This serial of patches fix resource leak in error paths.
All applied, thanks - thanks for taking the time to do so many cleanups
recently, it's appreciated.
next prev parent reply other threads:[~2010-11-25 11:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 7:06 [PATCH 0/8] ASoC: fix resource leak in error paths Axel Lin
2010-11-25 7:07 ` [PATCH 1/8] ASoC: efika-audio-fabric: fix resource leak in efika_fabric_init error path Axel Lin
2010-11-25 7:08 ` [PATCH 2/8] ASoC: pcm030-audio-fabric: fix resource leak in pcm030_fabric_init " Axel Lin
2010-11-25 7:10 ` [PATCH 3/8] ASoC: snd-soc-afeb9260: remove unneeded platform_device_del in " Axel Lin
2010-11-25 7:11 ` [PATCH 4/8] ASoC: sam9g20_wm8731: fix resource leak in at91sam9g20ek_init " Axel Lin
2010-11-25 7:11 ` [PATCH 5/8] ASoC: smdk_wm9713: fix resource leak in smdk_init " Axel Lin
2010-11-25 7:12 ` [PATCH 6/8] ASoC: simone: fix resource leak in simone_init " Axel Lin
2010-11-25 8:06 ` Mika Westerberg
2010-11-25 8:06 ` Mika Westerberg
2010-11-25 7:13 ` [PATCH 7/8] ASoC: imx-ssi: fix resource leak Axel Lin
2010-11-25 9:19 ` Sascha Hauer
2010-11-25 9:19 ` Sascha Hauer
2010-11-25 7:14 ` [PATCH 8/8] ASoC: phycore-ac97: " Axel Lin
2010-11-25 9:19 ` Sascha Hauer
2010-11-25 9:19 ` Sascha Hauer
2010-11-25 10:47 ` [PATCH 0/8] ASoC: fix resource leak in error paths Liam Girdwood
2010-11-25 10:47 ` Liam Girdwood
2010-11-25 11:14 ` Mark Brown [this message]
2010-11-25 11:14 ` 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=20101125111444.GD22298@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=jassi.brar@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mika.westerberg@iki.fi \
--cc=s.hauer@pengutronix.de \
--cc=sedji.gaouaou@atmel.com \
--cc=slapin@ossfans.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.