From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question about your DSP topic branch
Date: Mon, 31 Jan 2011 13:30:15 +0000 [thread overview]
Message-ID: <20110131133015.GI5123@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D41E8FE.4070206@codeaurora.org>
On Thu, Jan 27, 2011 at 01:51:58PM -0800, Patrick Lai wrote:
> On 1/26/2011 3:20 AM, Mark Brown wrote:
> >Yup, but it's not really a big cost - they're all so trivial.
> Currently, I already have few dummy codec drivers in mind for the
> project I am working on. I am not worried about the size of these
> files. Beside having tons of dummy codec drivers in the source tree,
> I am also looking at the value and effort to upstream these trivial
> drivers.
Like I say, it's utterly trivial.
next prev parent reply other threads:[~2011-01-31 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2652C8.7030701@codeaurora.org>
2011-01-25 7:01 ` Question about your DSP topic branch Patrick Lai
2011-01-25 11:51 ` Mark Brown
2011-01-26 6:22 ` Patrick Lai
2011-01-26 11:20 ` Mark Brown
2011-01-27 21:51 ` Patrick Lai
2011-01-31 13:30 ` Mark Brown [this message]
2011-03-17 7:29 ` Patrick Lai
2011-03-17 11:57 ` Mark Brown
2011-01-25 16:46 ` Liam Girdwood
2011-01-27 23:41 ` Patrick Lai
2011-03-15 7:08 ` [alsa-devel] " Patrick Lai
2011-03-15 11:25 ` Mark Brown
2011-03-17 7:21 ` Patrick Lai
2011-03-17 23:58 ` Mark Brown
2011-03-30 20:39 ` Question about your DSP topic Patrick Lai
2011-03-31 6:40 ` Question about your DSP topic branch Patrick Lai
2011-03-31 21:35 ` Liam Girdwood
2011-03-31 21:42 ` Mark Brown
2011-03-31 22:07 ` Patrick Lai
2011-03-31 18:26 ` Question about your DSP topic Liam Girdwood
2011-03-31 20:59 ` Patrick Lai
2011-03-31 21:37 ` Liam Girdwood
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=20110131133015.GI5123@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=plai@codeaurora.org \
/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.