From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Joonyoung Shim <jy0922.shim@samsung.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
kyungmin.park@samsung.com
Subject: Re: ASoC status to support multiple CODECs?
Date: Wed, 24 Feb 2010 09:30:52 +0000 [thread overview]
Message-ID: <1267003852.3274.17.camel@odin> (raw)
In-Reply-To: <4B849104.50401@samsung.com>
On Wed, 2010-02-24 at 11:37 +0900, Joonyoung Shim wrote:
> Hi,
>
> Can i know the work progress status to support multiple CODECs at the
> ASoC? I just wonder.
>
I've not started development yet as I've had other higher priority work.
I also can't give a date for starting this atm, please feel free to give
it a go yourself.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-02-24 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 2:37 ASoC status to support multiple CODECs? Joonyoung Shim
2010-02-24 9:30 ` Liam Girdwood [this message]
2010-02-25 2:43 ` Joonyoung Shim
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=1267003852.3274.17.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.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