public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: vinod.koul@intel•com (Vinod Koul)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2] dma: imx-sdma: Add ROM script addresses to driver
Date: Mon, 26 Aug 2013 20:47:54 +0530	[thread overview]
Message-ID: <20130826151754.GR2748@intel.com> (raw)
In-Reply-To: <1376985873-25776-1-git-send-email-s.hauer@pengutronix.de>

On Tue, Aug 20, 2013 at 10:04:30AM +0200, Sascha Hauer wrote:
> Changes since v1:
> 
> - skip handling of SoCs which have a tapeout specific SDMA firmware,
>   namely i.MX31/35
Applied, with typo fix in patch 1...

~Vinod

      parent reply	other threads:[~2013-08-26 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  8:04 [PATCH v2] dma: imx-sdma: Add ROM script addresses to driver Sascha Hauer
2013-08-20  8:04 ` [PATCH 1/3] dma: imx-sdma: Use struct for driver data Sascha Hauer
2013-08-26 15:19   ` Vinod Koul
2013-08-20  8:04 ` [PATCH 2/3] dma: imx-sdma: Add ROM script addresses to driver Sascha Hauer
2013-08-20  8:04 ` [PATCH 3/3] ARM: i.MX: remove sdma script address arrays from platform data Sascha Hauer
2013-08-20  8:52 ` [PATCH v2] dma: imx-sdma: Add ROM script addresses to driver Shawn Guo
2013-08-22  7:13 ` Sascha Hauer
2013-08-26 15:17 ` Vinod Koul [this message]

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=20130826151754.GR2748@intel.com \
    --to=vinod.koul@intel$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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