From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Mark Brown <broonie@kernel.org>
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
Subject: Re: [PATCH] ASoC: rsnd: fix src clock prepare/unprepare
Date: Mon, 31 Mar 2014 11:05:32 +0100 [thread overview]
Message-ID: <53393DEC.9060400@codethink.co.uk> (raw)
In-Reply-To: <20140330222433.GJ2269@sirena.org.uk>
On 30/03/14 23:24, Mark Brown wrote:
> On Sun, Mar 30, 2014 at 02:36:34PM +0100, Ben Dooks wrote:
>> On 29/03/14 10:10, Mark Brown wrote:
>>>> sound/soc/sh/rcar/scu.c | 4 ++--
>
>> It was against your current development branch which is
>> what we having been testing against (due to the large number
>> of commits in the rcar area)
>
> 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.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
WARNING: multiple messages have this Message-ID (diff)
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Mark Brown <broonie@kernel.org>
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
Subject: Re: [PATCH] ASoC: rsnd: fix src clock prepare/unprepare
Date: Mon, 31 Mar 2014 10:05:32 +0000 [thread overview]
Message-ID: <53393DEC.9060400@codethink.co.uk> (raw)
In-Reply-To: <20140330222433.GJ2269@sirena.org.uk>
On 30/03/14 23:24, Mark Brown wrote:
> On Sun, Mar 30, 2014 at 02:36:34PM +0100, Ben Dooks wrote:
>> On 29/03/14 10:10, Mark Brown wrote:
>>>> sound/soc/sh/rcar/scu.c | 4 ++--
>
>> It was against your current development branch which is
>> what we having been testing against (due to the large number
>> of commits in the rcar area)
>
> 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.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-31 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 15:03 [PATCH] ASoC: rsnd: fix src clock prepare/unprepare Ben Dooks
2014-03-29 10:10 ` Mark Brown
2014-03-30 13:36 ` Ben Dooks
2014-03-30 13:36 ` Ben Dooks
2014-03-30 22:24 ` Mark Brown
2014-03-30 22:24 ` Mark Brown
2014-03-31 10:05 ` Ben Dooks [this message]
2014-03-31 10:05 ` Ben Dooks
2014-03-31 10:18 ` Mark Brown
2014-03-31 10:18 ` Mark Brown
2014-03-31 10:30 ` Ben Dooks
2014-03-31 10:30 ` Ben Dooks
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=53393DEC.9060400@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@opensource.se \
/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.