From: Vinod Koul <vinod.koul@linux.intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic()
Date: Mon, 24 Sep 2012 14:10:09 +0530 [thread overview]
Message-ID: <1348476009.1943.187.camel@vkoul-udesk3> (raw)
In-Reply-To: <1348473485-5081-1-git-send-email-peter.ujfalusi@ti.com>
On Mon, 2012-09-24 at 10:58 +0300, Peter Ujfalusi wrote:
> 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.
I though patch 1 was part of the series Mark was supposed to apply.
Anyway both look fine to me so:
Both Acked-By: Vinod Koul <vinod.koul@linux.intel.com>
--
~Vinod
next prev parent reply other threads:[~2012-09-24 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 3:39 linux-next: build failure after merge of the sound and sound-asoc trees Stephen Rothwell
2012-09-24 7:48 ` Takashi Iwai
2012-09-24 7:52 ` Peter Ujfalusi
2012-09-24 7:58 ` [PATCH 0/2] dmaengine: Fix compillation issues in device_prep_dma_cyclic() Peter Ujfalusi
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 ` [alsa-devel] " Mark Brown
2012-09-24 8:40 ` Vinod Koul [this message]
2012-10-12 16:44 ` 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=1348476009.1943.187.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.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=peter.ujfalusi@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®