From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM
Date: Fri, 17 Feb 2012 10:47:58 +0000 [thread overview]
Message-ID: <1329475678.3972.20.camel@odin> (raw)
In-Reply-To: <20120217054339.GB1231@opensource.wolfsonmicro.com>
On Thu, 2012-02-16 at 21:43 -0800, Mark Brown wrote:
> On Fri, Feb 17, 2012 at 11:10:53AM +0530, Vinod Koul wrote:
> > On Thu, 2012-02-16 at 09:59 -0800, Mark Brown wrote:
>
> > > I *think* can get something working quickly that doesn't fill in the
> > > blanks for CODEC-CODEC links, though the conference is looking quite
> > > interesting today. I'll try to send something later.
>
> > On conference, when are we planing our next ASoC conference?
>
> Not at present. It would probably have been colocated with ELC but
> that didn't happen.
Sadly I didn't have enough time to set this up for ELC but I should have
more time after Dynamic PCM is upstream. I've had some discussions with
the Linux Foundation and they are happy to co-locate. Lets discuss when
you get back in the UK.
Liam
prev parent reply other threads:[~2012-02-17 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:02 [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM Liam Girdwood
2012-02-15 16:02 ` [PATCH 2/2] ASoC: core - Add support for direct DAI -> widget mapping stream events Liam Girdwood
2012-02-15 16:24 ` [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM Mark Brown
2012-02-16 13:35 ` Liam Girdwood
2012-02-16 17:59 ` Mark Brown
2012-02-17 5:40 ` Vinod Koul
2012-02-17 5:43 ` Mark Brown
2012-02-17 10:47 ` Liam Girdwood [this message]
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=1329475678.3972.20.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=vinod.koul@linux.intel.com \
/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.