Hi Mark,

On Mon, 16 Aug 2010 17:34:57 +0100 Mark Brown broonie@opensource.wolfsonmicro.com wrote:

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.

Added from today - called sound-asoc. I will merge it before the main sound tree so we see the conflicts in this tree and (hopefully) not in the main sound tree.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.