From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ASoC: atmel-pcm: split into two file
Date: Sun, 2 Dec 2012 13:28:27 +0900 [thread overview]
Message-ID: <20121202042826.GV17981@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1354074373-7671-1-git-send-email-voice.shen@atmel.com>
On Wed, Nov 28, 2012 at 11:46:12AM +0800, Bo Shen wrote:
> This patch is split original atmel-pcm.c into new atmel-pcm.c and
> atmel-pcm-pdc.c two files. The new atmel-pcm.c is the share routine
> while will be used for pdc or dma transfer.
>
> Using SND_ATMEL_SOC_PDC to select using PDC for audio transfer
Applied, thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121202/e50543f9/attachment.sig>
prev parent reply other threads:[~2012-12-02 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 3:46 [PATCH 1/2] ASoC: atmel-pcm: split into two file Bo Shen
2012-11-28 3:46 ` [PATCH 2/2] ASoC: atmel-pcm: dma support based on pcm dmaengine Bo Shen
2012-12-02 4:30 ` Mark Brown
2012-12-02 4:28 ` 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=20121202042826.GV17981@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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 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).