From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Temporary ASoC tree for next
Date: Mon, 16 Aug 2010 17:34:57 +0100 [thread overview]
Message-ID: <20100816163457.GF3276@rakim.wolfsonmicro.main> (raw)
Hi Stephen,
Liam has recently done some work on ASoC to enhance the ability to work
with multiple external devices which we're expecting to get in for .37.
Since this work required some architecture modifications and we've had a
bit of trouble getting testers we're expecting a higher than average
degree of cross-tree issues this cycle so in order to avoid affecting
all other ALSA work we'd like to have a separate ASoC-specific tree in
-next for this release cycle if possible:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-next
Please also include Liam as a contact for the tree.
Thanks,
Mark
next reply other threads:[~2010-08-16 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 16:34 Mark Brown [this message]
2010-08-17 0:59 ` Temporary ASoC tree for next Stephen Rothwell
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=20100816163457.GF3276@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
--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).