From: Sascha Hauer <s.hauer@pengutronix.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-arm-kernel@lists.infradead.org,
Vinod Koul <vinod.koul@intel.com>,
Javier Martin <javier.martin@vista-silicon.com>,
linux-kernel@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 2/4] ASoC: i.MX: Add missing dma_async_issue_pending
Date: Tue, 10 Jan 2012 09:39:22 +0100 [thread overview]
Message-ID: <20120110083922.GT5446@pengutronix.de> (raw)
In-Reply-To: <20120109161301.GB2974@opensource.wolfsonmicro.com>
On Mon, Jan 09, 2012 at 08:13:02AM -0800, Mark Brown wrote:
> On Mon, Jan 09, 2012 at 10:32:48AM +0100, Sascha Hauer wrote:
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> but I guess I can just apply it immediately?
The ASoC patch (also the mmc driver patch) have to be applied
before the dma driver patches. To make this sure I think it's
best when Vinoud applies the whole series.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-01-10 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 9:32 [PATCH] fix starting of transfers in i.MX dma drivers Sascha Hauer
2012-01-09 9:32 ` [PATCH 1/4] mmc: mxcmmc: add missing dma_async_issue_pending Sascha Hauer
2012-01-09 9:32 ` [PATCH 2/4] ASoC: i.MX: Add " Sascha Hauer
2012-01-09 16:13 ` Mark Brown
2012-01-10 8:39 ` Sascha Hauer [this message]
2012-01-09 9:32 ` [PATCH 3/4] dma: imx-dma: start transfer in issue_pending Sascha Hauer
2012-01-09 10:51 ` Russell King - ARM Linux
2012-01-09 9:32 ` [PATCH 4/4] dma: imx-sdma: " Sascha Hauer
2012-01-12 12:25 ` [PATCH] fix starting of transfers in i.MX dma drivers javier Martin
2012-01-15 17:07 ` Koul, Vinod
2012-01-30 9:12 ` Vinod Koul
2012-01-30 12:22 ` javier Martin
2012-01-30 14: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=20120110083922.GT5446@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=javier.martin@vista-silicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox