From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: fabio.estevam@freescale.com, alsa-devel@alsa-project.org,
samuel@sortiz.org, vinod.koul@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, paul.gortmaker@windriver.com,
linux-next@vger.kernel.org, tiwai@suse.de,
dan.j.williams@intel.com, lrg@ti.com
Subject: Re: [PATCH linux-next] dmaengine: add context parameter fixups
Date: Sat, 24 Mar 2012 00:53:20 +0000 [thread overview]
Message-ID: <20120324005320.GB3190@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332511242-30241-1-git-send-email-alexandre.bounine@idt.com>
[-- Attachment #1.1: Type: text/plain, Size: 326 bytes --]
On Fri, Mar 23, 2012 at 10:00:42AM -0400, Alexandre Bounine wrote:
> This patch fixes drivers that use device_prep_slave_sg() and
> device_prep_dma_cyclic() interfaces and have been missed during the initial
> release of interface changing patches.
Can you please send a separate patch for the ASoC (sound/soc) bits of
this?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-24 0:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:00 [PATCH linux-next] dmaengine: add context parameter fixups Alexandre Bounine
2012-03-24 0:53 ` Mark Brown [this message]
2012-03-24 15:23 ` Fabio Estevam
2012-03-26 5:34 ` Vinod Koul
2012-03-26 9:42 ` Mark Brown
2012-03-26 9:54 ` Vinod Koul
2012-03-26 10:33 ` Mark Brown
2012-03-26 10:48 ` Vinod Koul
2012-03-26 11:01 ` Mark Brown
2012-03-26 11:07 ` Vinod Koul
2012-03-26 13:14 ` Bounine, Alexandre
2012-03-28 15:44 ` Takashi Iwai
2012-03-28 15:51 ` Mark Brown
2012-03-29 10:59 ` Vinod Koul
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=20120324005320.GB3190@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alexandre.bounine@idt.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan.j.williams@intel.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=samuel@sortiz.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@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).