From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
paul.gortmaker@windriver.com, fabio.estevam@freescale.com,
Alexandre.Bounine@idt.com
Subject: Re: [PATCH] ASoC: dmaengine_pcm: use dmaengine cyclic wrapper
Date: Mon, 26 Mar 2012 18:28:37 +0100 [thread overview]
Message-ID: <20120326172837.GA3789@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332763088-18964-1-git-send-email-vinod.koul@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
On Mon, Mar 26, 2012 at 05:28:08PM +0530, Vinod Koul wrote:
> commit 4a163c82 added extra parameter to device_prep_dma_cyclic
> this is not required if we use the wrapper over cyclic API.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-26 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 11:58 [PATCH] ASoC: dmaengine_pcm: use dmaengine cyclic wrapper Vinod Koul
2012-03-26 17: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=20120326172837.GA3789@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Alexandre.Bounine@idt.com \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=vinod.koul@linux.intel.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).