alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
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.35
Date: Mon, 29 Mar 2010 21:13:11 +0100	[thread overview]
Message-ID: <20100329201310.GA7256@rakim.wolfsonmicro.main> (raw)

The following changes since commit 923a00427a141a6d1c83f1b151221a2458b2de8d:
  Tejun Heo (1):
        ASoC: update gfp/slab.h includes

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.35

Barry Song (1):
      ASoC: ad193x: move codec register/unregister to bus probe/remove

Dan Carpenter (1):
      ASoC: wm8994: playback => capture

Graham Gower (1):
      ASoC: Fix passing platform_data to ac97 bus users and fix a leak

Kuninori Morimoto (4):
      ASoC: fsi: ensures process inside master lock
      ASoC: fsi: IRQ related process had be united
      ASoC: fsi: Add FIFO size calculate
      ASoC: fsi: Add FSI2 device support

Mark Brown (2):
      Merge branch 'topic/asoc' of git://git.kernel.org/.../tiwai/sound-2.6 into for-2.6.35
      Merge branch 'for-2.6.34' into for-2.6.35

 sound/soc/codecs/ac97.c   |   15 ++--
 sound/soc/codecs/ad193x.c |  102 ++++++++++--------------
 sound/soc/codecs/wm8994.c |    2 +-
 sound/soc/sh/Kconfig      |    3 +-
 sound/soc/sh/fsi.c        |  191 ++++++++++++++++++++++++++++++++-------------
 sound/soc/soc-core.c      |    3 +-
 6 files changed, 192 insertions(+), 124 deletions(-)

             reply	other threads:[~2010-03-29 20:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 20:13 Mark Brown [this message]
2010-03-30  6:08 ` ASoC updates for 2.6.35 Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2010-07-13 11:43 Mark Brown
2010-07-13 15:09 ` Takashi Iwai
2010-06-02 10:46 Mark Brown
2010-06-02 12:20 ` Takashi Iwai
2010-05-26 15:50 Mark Brown
2010-05-27  8:09 ` Takashi Iwai
2010-05-11 13:38 Mark Brown
2010-05-11 13:47 ` Takashi Iwai
2010-05-10 17:15 Mark Brown
2010-05-11  8:00 ` Takashi Iwai
2010-05-07 16:46 Mark Brown
2010-05-08  9:45 ` Takashi Iwai
2010-04-30 15:35 Mark Brown
2010-05-05  8:04 ` Takashi Iwai
2010-04-26 15:16 Mark Brown
2010-04-26 15:35 ` Takashi Iwai
2010-04-22  0:16 Mark Brown
2010-04-22  7:13 ` Takashi Iwai
2010-04-20  0:58 Mark Brown
2010-04-20  6:32 ` Takashi Iwai
2010-04-20 16:36   ` Mark Brown
2010-04-13  8:53 Mark Brown
2010-04-13 10:03 ` Takashi Iwai
2010-04-05 18:44 Mark Brown
2010-04-05 19:29 ` Takashi Iwai
2010-03-23 15:52 Mark Brown
2010-03-23 16:31 ` Takashi Iwai
2010-03-22 21:23 Mark Brown
2010-03-23  7:02 ` Takashi Iwai
2010-03-19 15:30 Mark Brown
2010-03-19 20:35 ` Takashi Iwai
2010-03-18 15:57 Mark Brown
2010-03-18 16:46 ` Takashi Iwai
2010-03-17 14:26 Mark Brown
2010-03-17 14:31 ` Takashi Iwai
2010-03-16 16:15 Mark Brown
2010-03-16 17:34 ` Takashi Iwai
2010-03-17 13:42 ` Takashi Iwai
2010-03-17 13:44   ` Mark Brown
2010-03-17 13:46     ` Takashi Iwai
2010-03-12 18:08 Mark Brown
2010-03-13 16:11 ` Takashi Iwai
2010-03-10 15:35 Mark Brown
2010-03-10 19:05 ` 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=20100329201310.GA7256@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).