From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Merge of 2.6.32-rc3 into fix/asoc
Date: Tue, 6 Oct 2009 13:03:23 +0100 [thread overview]
Message-ID: <20091006120323.GD10118@rakim.wolfsonmicro.main> (raw)
I've pushed an update of the fix/asoc branch which has 2.6.32-rc3 merged
up to my git. This gets underlying platform support from other trees
into the branch and will also (once it's merged up there) give topic/asoc
access to things like the genirq improvements for I2C and SPI devices
which were merged during the merge window.
The following changes since commit e655a43544bd3c45a83da93b00a4b115b4fa758e:
Jonathan Cameron (1):
ASoC: wm8940: Fix check on error code form snd_soc_codec_set_cache_io
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.32-merge
Changelog omitted - the only changes since your fix/asoc should be those
from Linus' tree and the merge commit.
next reply other threads:[~2009-10-06 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 12:03 Mark Brown [this message]
2009-10-06 12:44 ` Merge of 2.6.32-rc3 into fix/asoc Takashi Iwai
2009-10-06 12:47 ` Mark Brown
2009-10-06 12:51 ` 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=20091006120323.GD10118@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--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.