At Fri, 1 Mar 2013 21:46:16 +1030, Jonathan Woithe wrote:
Hi Takashi
On Wed, Feb 20, 2013 at 02:14:20PM +0100, Takashi Iwai wrote:
Sounds good - I will test in the next day or so and report back. What's the most efficient way to get hold of this tree / branch given that I have the for-next branch of sound.git? Can I somehow leverage this, or do I need to do a completely separate checkout? Apologies if this is a basic question - I'm still coming to terms with git.
sound-unstable git tree always contains the sound git tree master branch, so everything is there basically. ...
What's the next step in the process? I've reported the outcome of the tests of sound-unstable as per that report progress is being made. Is it a case of waiting for things to stabilise, or do you need me to do something to move things along? If so, what?
I merged the patches to the main sound git tree for-next branch now.
Also a few updates are merged there, too: now the hp mic jack mode should be able to change the pin control no matter whether which capture source is. Also, the capture source won't change the hp/mic pinctl when the jack mode enum is created. This reduces the automation but also reduces the confusion, too. After all, when jack mode is present, user wants to control the pin by himself.
Let me know if anything else is missing or broken.
thanks,
Takashi