From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
Kukjin Kim <kgene.kim@samsung.com>
Subject: [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic()
Date: Mon, 24 Sep 2012 10:58:03 +0300 [thread overview]
Message-ID: <1348473485-5081-1-git-send-email-peter.ujfalusi@ti.com> (raw)
In-Reply-To: <20120924133923.130c4db72aa8105cb5647d7a@canb.auug.org.au>
Hello,
The reason for the breakage is the patch 1 got lost somewhere in the process.
I also greped the whole tree for device_prep_dma_cyclic() and the second patch
is the result of that.
PS: I did build tested the series on ARM (OMAP), x86_32, x86_64 but not for ppc
for sure.
Regards,
Peter
---
Peter Ujfalusi (2):
dmaengine: Add flags parameter to dmaengine_prep_dma_cyclic()
ARM: SAMSUNG: dma-ops: Fix dmaengine_prep_dma_cyclic() parameter list
arch/arm/plat-samsung/dma-ops.c | 3 ++-
include/linux/dmaengine.h | 3 ++-
sound/soc/soc-dmaengine-pcm.c | 6 +++++-
3 files changed, 9 insertions(+), 3 deletions(-)
--
1.7.12
next parent reply other threads:[~2012-09-24 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120924133923.130c4db72aa8105cb5647d7a@canb.auug.org.au>
2012-09-24 7:58 ` Peter Ujfalusi [this message]
2012-09-24 7:58 ` [PATCH 1/2] dmaengine: Add flags parameter to dmaengine_prep_dma_cyclic() Peter Ujfalusi
2012-09-24 7:58 ` [PATCH 2/2] ARM: SAMSUNG: dma-ops: Fix dmaengine_prep_dma_cyclic() parameter list Peter Ujfalusi
2012-09-24 8:17 ` [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic() Takashi Iwai
2012-09-24 18:08 ` Takashi Iwai
2012-09-25 11:19 ` Mark Brown
2012-09-24 8:40 ` Vinod Koul
2012-10-12 16:44 ` [alsa-devel] " Tabi Timur-B04825
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=1348473485-5081-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sfr@canb.auug.org.au \
--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).