From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: ASoC updates for 2.6.36
Date: Tue, 3 Aug 2010 10:09:22 +0100 [thread overview]
Message-ID: <20100803090922.GD25306@rakim.wolfsonmicro.main> (raw)
The following changes since commit 988b0dc1547f9f6a7c8cae472cad0a55df31818c:
Merge branch 'for-2.6.36' of git://git.kernel.org/pub/scm/linux/kernel/git/lrg/asoc-2.6 into topic/asoc (2010-08-02 12:10:52 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.36
Axel Lin (12):
ASoC: ad1836: fix a memory leak if another ad1836 is registered
ASoC: ak4642: fix a memory leak if failed to initialise AK4642
ASoC: da7210: fix a memory leak if failed to initialise da7210 audio codec
ASoC: wm8523: fix resource reclaim in wm8523_register error path
ASoC: wm8711: fix a memory leak if another WM8711 is registered
ASoC: wm8904: fix resource reclaim in wm8904_register error path
ASoC: wm8940: fix a memory leak if wm8940_register return error
ASoC: wm8955: fix resource reclaim in wm8955_register error path
ASoC: wm8961: fix resource reclaim in wm8961_register error path
ASoC: wm8974: fix a memory leak if another WM8974 is registered
ASoC: wm8978: fix a memory leak if a wm8978_register fail
ASoC: wm9081: fix resource reclaim in wm9081_register error path
Ian Lartey (1):
ASoC: Initial WM8741 CODEC driver
sound/soc/codecs/Kconfig | 4 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/ad1836.c | 1 +
sound/soc/codecs/ak4642.c | 4 +-
sound/soc/codecs/da7210.c | 8 +-
sound/soc/codecs/wm8523.c | 10 +-
sound/soc/codecs/wm8711.c | 3 +-
sound/soc/codecs/wm8741.c | 579 +++++++++++++++++++++++++++++++++++++++++++++
sound/soc/codecs/wm8741.h | 214 +++++++++++++++++
sound/soc/codecs/wm8904.c | 13 +-
sound/soc/codecs/wm8940.c | 7 +-
sound/soc/codecs/wm8955.c | 10 +-
sound/soc/codecs/wm8961.c | 9 +-
sound/soc/codecs/wm8974.c | 3 +-
sound/soc/codecs/wm8978.c | 10 +-
sound/soc/codecs/wm9081.c | 11 +-
16 files changed, 857 insertions(+), 31 deletions(-)
create mode 100644 sound/soc/codecs/wm8741.c
create mode 100644 sound/soc/codecs/wm8741.h
next reply other threads:[~2010-08-03 9:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 9:09 Mark Brown [this message]
2010-08-03 9:55 ` ASoC updates for 2.6.36 Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 21:16 Mark Brown
2010-10-11 11:59 ` Takashi Iwai
2010-08-13 14:49 Mark Brown
2010-08-13 16:12 ` Takashi Iwai
2010-08-10 14:52 Mark Brown
2010-08-10 14:56 ` Takashi Iwai
2010-07-29 17:55 Mark Brown
2010-07-29 18:06 ` Takashi Iwai
2010-07-20 12:43 Mark Brown
2010-07-20 14:39 ` Takashi Iwai
2010-07-08 23:56 Mark Brown
2010-07-09 8:11 ` Takashi Iwai
2010-07-06 0:21 Mark Brown
2010-07-06 6:23 ` Takashi Iwai
2010-07-01 18:43 Mark Brown
2010-07-04 9:23 ` Mark Brown
2010-07-05 7:00 ` Takashi Iwai
2010-06-22 23:27 Mark Brown
2010-06-23 7:46 ` Takashi Iwai
2010-06-16 14:23 Mark Brown
2010-06-16 16:06 ` Mark Brown
2010-06-16 17:31 ` Takashi Iwai
2010-06-15 11:34 Mark Brown
2010-06-15 13:05 ` Takashi Iwai
2010-06-07 13:41 Mark Brown
2010-06-07 16:42 ` Takashi Iwai
2010-05-31 13:03 Mark Brown
2010-05-31 16:15 ` Takashi Iwai
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=20100803090922.GD25306@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
/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.