From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org,
Dong Aisheng <dong.aisheng@linaro.org>,
linux-kernel@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>,
Liam Girdwood <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] ASoC: mxs: correct 'direction' of device_prep_dma_cyclic
Date: Fri, 23 Dec 2011 16:28:27 +0000 [thread overview]
Message-ID: <20111223162826.GA28036@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1324656420.1633.15.camel@vkoul-udesk3>
On Fri, Dec 23, 2011 at 09:37:00PM +0530, Vinod Koul wrote:
> Has this been applied in soc tree? I don't see it in linux-next or do
> you want this to go thru slave-dma?
I reverted it, it needs to go with the commit that introduces the new
API otherwise it breaks bisection.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ASoC: mxs: correct 'direction' of device_prep_dma_cyclic
Date: Fri, 23 Dec 2011 16:28:27 +0000 [thread overview]
Message-ID: <20111223162826.GA28036@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1324656420.1633.15.camel@vkoul-udesk3>
On Fri, Dec 23, 2011 at 09:37:00PM +0530, Vinod Koul wrote:
> Has this been applied in soc tree? I don't see it in linux-next or do
> you want this to go thru slave-dma?
I reverted it, it needs to go with the commit that introduces the new
API otherwise it breaks bisection.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Shawn Guo <shawn.guo@linaro.org>, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org,
Dong Aisheng <dong.aisheng@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] ASoC: mxs: correct 'direction' of device_prep_dma_cyclic
Date: Fri, 23 Dec 2011 16:28:27 +0000 [thread overview]
Message-ID: <20111223162826.GA28036@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1324656420.1633.15.camel@vkoul-udesk3>
On Fri, Dec 23, 2011 at 09:37:00PM +0530, Vinod Koul wrote:
> Has this been applied in soc tree? I don't see it in linux-next or do
> you want this to go thru slave-dma?
I reverted it, it needs to go with the commit that introduces the new
API otherwise it breaks bisection.
next prev parent reply other threads:[~2011-12-23 16:28 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 15:48 [PATCH 0/4] Fix the left DMA_NONE from dma_transfer_direction migration Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` [PATCH 1/4] dmaengine: add DMA_TRANS_NONE to dma_transfer_direction Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` [PATCH 2/4] mmc: mxs-mmc: fix the dma_transfer_direction migration Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` [PATCH 3/4] mtd: fix compile error for gpmi-nand Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-14 2:21 ` Huang Shijie
2011-12-14 2:21 ` Huang Shijie
2011-12-14 2:21 ` Huang Shijie
2011-12-14 2:21 ` Huang Shijie
2011-12-13 15:48 ` [PATCH 4/4] mtd: gpmi-nand: move to dma_transfer_direction Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-13 15:48 ` Shawn Guo
2011-12-14 2:20 ` Huang Shijie
2011-12-14 2:20 ` Huang Shijie
2011-12-14 2:20 ` Huang Shijie
2011-12-14 2:20 ` Huang Shijie
2011-12-14 7:47 ` [PATCH 5/5] ASoC: mxs: correct 'direction' of device_prep_dma_cyclic Shawn Guo
2011-12-14 7:47 ` Shawn Guo
2011-12-14 7:47 ` Shawn Guo
2011-12-14 8:49 ` Dong Aisheng-B29396
2011-12-14 8:49 ` Dong Aisheng-B29396
2011-12-20 0:51 ` Mark Brown
2011-12-20 0:51 ` Mark Brown
2011-12-20 0:51 ` Mark Brown
2011-12-20 3:07 ` [alsa-devel] " Shawn Guo
2011-12-20 3:07 ` Shawn Guo
2011-12-20 3:07 ` Shawn Guo
2011-12-23 16:07 ` Vinod Koul
2011-12-23 16:07 ` Vinod Koul
2011-12-23 16:07 ` Vinod Koul
2011-12-23 16:28 ` Mark Brown [this message]
2011-12-23 16:28 ` Mark Brown
2011-12-23 16:28 ` Mark Brown
2011-12-23 16:32 ` Vinod Koul
2011-12-23 16:32 ` Vinod Koul
2011-12-23 16:32 ` Vinod Koul
2011-12-20 9:24 ` [PATCH 0/4] Fix the left DMA_NONE from dma_transfer_direction migration Vinod Koul
2011-12-20 9:24 ` Vinod Koul
2011-12-20 9:24 ` Vinod Koul
2011-12-20 12:54 ` Shawn Guo
2011-12-20 12:54 ` Shawn Guo
2011-12-20 12:54 ` Shawn Guo
2011-12-20 12:54 ` Shawn Guo
2011-12-21 4:07 ` Vinod Koul
2011-12-21 4:07 ` Vinod Koul
2011-12-21 4:07 ` Vinod Koul
2011-12-21 4:45 ` Shawn Guo
2011-12-21 4:45 ` Shawn Guo
2011-12-21 4:45 ` Shawn Guo
2011-12-21 4:45 ` Shawn Guo
2011-12-21 4:40 ` Vinod Koul
2011-12-21 4:40 ` Vinod Koul
2011-12-21 4:40 ` Vinod Koul
2011-12-21 4:58 ` Shawn Guo
2011-12-21 4:58 ` Shawn Guo
2011-12-21 4:58 ` Shawn Guo
2011-12-21 4:58 ` Shawn Guo
2011-12-22 5:13 ` Vinod Koul
2011-12-22 5:13 ` Vinod Koul
2011-12-22 5:13 ` Vinod Koul
2011-12-23 16:03 ` Vinod Koul
2011-12-23 16:03 ` Vinod Koul
2011-12-23 16:03 ` 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=20111223162826.GA28036@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dong.aisheng@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=shawn.guo@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.