From: Barry Song <21cnbao@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>,
DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>,
Rongjun Ying <Rongjun.Ying@csr.com>,
Barry Song <Baohua.Song@csr.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 4/6] ASoC: sirf-soc-inner: add drivers for both CPU and Codec DAIs
Date: Tue, 29 Oct 2013 16:32:21 +0800 [thread overview]
Message-ID: <CAGsJ_4xG6KaxrrrsaWJi9K3444JFT5h6sB-qV2VK8++NXuXkaQ@mail.gmail.com> (raw)
In-Reply-To: <20131028233603.GA16686@sirena.org.uk>
2013/10/29 Mark Brown <broonie@kernel.org>:
> On Tue, Oct 29, 2013 at 07:05:34AM +0800, Barry Song wrote:
>> From: Rongjun Ying <Rongjun.Ying@csr.com>
>>
>> there is an internal codec embedded in the SiRF SoC. this is not
>
> I've only got patch 4 - where are the other patches?
sorry i got some network problems and made some misoperations. others
have been in your mailboxs:
[PATCH v2 1/6] ASoC: sirf: add sirf platform driver which provides DMA
http://www.spinics.net/lists/arm-kernel/msg282590.html
[PATCH v2 2/6] ASoC: sirf: add I2S CPU DAI driver
http://www.spinics.net/lists/arm-kernel/msg282591.html
[PATCH v2 3/6] ASoC: usp-pcm: add CPU DAI driver for PCM simulated from USP
http://www.spinics.net/lists/arm-kernel/msg282592.html
...
-barry
prev parent reply other threads:[~2013-10-29 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 23:05 [PATCH v2 4/6] ASoC: sirf-soc-inner: add drivers for both CPU and Codec DAIs Barry Song
2013-10-28 23:36 ` Mark Brown
2013-10-29 8:32 ` Barry Song [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=CAGsJ_4xG6KaxrrrsaWJi9K3444JFT5h6sB-qV2VK8++NXuXkaQ@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=Rongjun.Ying@csr.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=workgroup.linux@csr.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).