From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Dooks Date: Mon, 31 Mar 2014 10:30:41 +0000 Subject: Re: [PATCH] ASoC: rsnd: fix src clock prepare/unprepare Message-Id: <533943D1.5010801@codethink.co.uk> List-Id: References: <1396018997-12390-1-git-send-email-ben.dooks@codethink.co.uk> <20140329101043.GF21628@sirena.org.uk> <53381DE2.9050907@codethink.co.uk> <20140330222433.GJ2269@sirena.org.uk> <53393DEC.9060400@codethink.co.uk> <20140331101827.GM2269@sirena.org.uk> In-Reply-To: <20140331101827.GM2269@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Mark Brown Cc: alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com, linux-sh@vger.kernel.org, magnus.damm@opensource.se, linux-kernel@lists.codethink.co.uk On 31/03/14 11:18, Mark Brown wrote: > On Mon, Mar 31, 2014 at 11:05:32AM +0100, Ben Dooks wrote: >> On 30/03/14 23:24, Mark Brown wrote: > >>> It would be easier to tell what you are talking about if you were to >>> quote some context from what you are replying to... I'm guessing this >>> is the file that doesn't exist, the above path not present in linux-next >>> so I don't know what you mean by my "current development branch". Are >>> you *sure* you're not using Linus' tree? > >> Why would I be using Linus' tree, it just /does not work/ at all. > >> I used your sound.git tree to work on due to the number of patches >> that where there. > > My git tree has many branches, which were you using? I'm pretty sure it > was neither the rcar topic branch nor for-next. I did merge in your "sound/topic/rcar" branch on 8th March, however I just noticed my colleague had cherry-picked patches off the list from earlier. If I see the file again I will re-send the patch. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius