From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Sebastien LEDUC <sebastien.leduc@st.com>
Subject: Re: dynamic PCM and dynamic DSP graphs
Date: Mon, 22 Oct 2012 13:04:26 +0100 [thread overview]
Message-ID: <20121022120426.GC4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <508130BD.4060909@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 339 bytes --]
On Fri, Oct 19, 2012 at 11:51:41AM +0100, Liam Girdwood wrote:
> Best to always CC Mark and I if you want a quicker reply from either of us.
Just to emphasise this point - for *all* Linux kernel things you should
always CC maintainers on mails. Things sent to the list only are liable
to get lost. It's not something specific to ASoC.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-10-22 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 9:39 dynamic PCM and dynamic DSP graphs Sebastien LEDUC
2012-10-19 10:51 ` Liam Girdwood
2012-10-19 11:56 ` Sebastien LEDUC
2012-10-19 14:36 ` Liam Girdwood
2012-10-22 12:04 ` Mark Brown [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=20121022120426.GC4477@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=sebastien.leduc@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).