linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Add device tree probe for imx-sdma driver
Date: Thu, 4 Aug 2011 13:35:04 +0800	[thread overview]
Message-ID: <20110804053504.GA3311@freescale.com> (raw)
In-Reply-To: <1312430372.1536.554.camel@vkoul-udesk3>

On Thu, Aug 04, 2011 at 09:29:32AM +0530, Koul, Vinod wrote:
> On Fri, 2011-07-15 at 17:44 +0800, Shawn Guo wrote:
> > The first patch remove the use of software defined sdma version, and
> > instead uses platform_device_id to handle the sdma differences from
> > one soc to another.  The second one makes a small cleanup on function
> > sdma_get_firmware(), and the third patch adds the actual device tree
> > probe support.
> > 
> > Changes since v1:
> >  * Do not encode ROM script address in device tree
> >  * Add one more small cleanup on function sdma_get_firmware()
> > 
> > ShawnsGuo (3):
> >       dmaengine: imx-sdma: use platform_device_id to identify sdma version
> >       dmaengine: imx-sdma: sdma_get_firmware does not need to copy fw_name
> >       dmaengine: imx-sdma: add device tree probe support
> > 
> Sacha are you okay if this go via my tree, would need your ack before I
> take this one
> 
Hi Vinod,

Sorry if I have misunderstood your reply below, but the series has
gone into mainline through arm tree.

Regards,
Shawn

---- Quote ---
On Mon, Jul 25, 2011 at 05:11:55PM +0530, Vinod Koul wrote:
> On Fri, 2011-07-22 at 11:54 +0800, Shawn Guo wrote:
> > Hi Vinod,
> >
> > Can I have your ack on this series, please?  I attempt to get it
> > merged through Sascha's tree after his tree and devicetree/next get
> > merged in the coming window.
> >
> > Regards,
> > Shawn
> >
> > On Fri, Jul 15, 2011 at 05:44:23PM +0800, Shawn Guo wrote:
> > >
> > > ShawnsGuo (3):
> > >       dmaengine: imx-sdma: use platform_device_id to identify sdma version
> > >       dmaengine: imx-sdma: sdma_get_firmware does not need to copy fw_name
> > >       dmaengine: imx-sdma: add device tree probe support
> > >
> Acked-by: Vinod Koul <vinod.koul@intel.com>
>
> I had queued this up for my tree, i am okay if it gets merged thru
> Sascha
>

  reply	other threads:[~2011-08-04  5:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  9:44 [PATCH v2 0/3] Add device tree probe for imx-sdma driver Shawn Guo
2011-07-15  9:44 ` [PATCH v2 1/3] dmaengine: imx-sdma: use platform_device_id to identify sdma version Shawn Guo
2011-09-05  9:16   ` Uwe Kleine-König
2011-07-15  9:44 ` [PATCH v2 2/3] dmaengine: imx-sdma: sdma_get_firmware does not need to copy fw_name Shawn Guo
2011-09-05  9:20   ` Uwe Kleine-König
2011-07-15  9:44 ` [PATCH v2 3/3] dmaengine: imx-sdma: add device tree probe support Shawn Guo
2011-08-04  3:57   ` Koul, Vinod
2011-08-25 13:37     ` Koul, Vinod
2011-08-30  1:45       ` Shawn Guo
2011-09-05  9:24   ` Uwe Kleine-König
2011-07-22  3:54 ` [PATCH v2 0/3] Add device tree probe for imx-sdma driver Shawn Guo
2011-07-25 11:41   ` Vinod Koul
2011-07-25 15:19     ` Shawn Guo
2011-08-04  3:59 ` Koul, Vinod
2011-08-04  5:35   ` Shawn Guo [this message]
2011-08-04  5:28     ` Koul, Vinod

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=20110804053504.GA3311@freescale.com \
    --to=shawn.guo@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).