mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: linux-kernel@vger.kernel.org,
	spear-devel <spear-devel@list.st.com>,
	viresh.kumar@linaro.org, Arnd Bergmann <arnd@arndb.de>,
	Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH v2 0/4] dw_dmac: move to own folder and split
Date: Tue, 11 Jun 2013 15:39:57 +0300	[thread overview]
Message-ID: <1370954397.29283.329.camel@smile> (raw)
In-Reply-To: <1370435206-13474-1-git-send-email-andriy.shevchenko@linux.intel.com>

On Wed, 2013-06-05 at 15:26 +0300, Andy Shevchenko wrote: 
> This is split of the dw_dmac driver as suggested by Arnd et al [1,2].
> There are three most important patches:
>  2/4 moves driver to its own folder
>  3/4 does the actual split
>  4/4 introduces PCI part of the driver
> 
> During this files are renamed: mostly means that dw_dmac prefix is eliminated.
> I hope to get it ready to be included in v3.11.
> 
> [1] http://www.spinics.net/lists/kernel/msg1408174.html
> [2] http://www.spinics.net/lists/kernel/msg1408495.html
> 
> Changes v1->v2:
>  - address Arnd's comments
>  - compile test when !CONFIG_PM
>  - apply ACKs
> 
> Cnages v0->v1:
>  - apply Viresh's ACKs
>  - append PCI part of the driver
>  - test altogether on Intel Medfield
>  - add 1/4 to the series as it based on it, but Vinod didn't apply it yet to
>    his tree.

Vinod, do you have any comments on this?

We would like to have this scheduled for v3.11.
I think we still have few days if you think we need to improve this
patchset.


-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  parent reply	other threads:[~2013-06-11 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 12:26 Andy Shevchenko
2013-06-05 12:26 ` [PATCH v2 1/4] dw_dmac: don't check resource with devm_ioremap_resource Andy Shevchenko
2013-06-05 12:26 ` [PATCH v2 2/4] dma: move dw_dmac driver to an own directory Andy Shevchenko
2013-06-12  5:08   ` Vinod Koul
2013-06-12  7:43     ` Andy Shevchenko
2013-06-12  7:39       ` Vinod Koul
2013-06-12  8:24         ` Viresh Kumar
2013-06-12  8:27         ` Andy Shevchenko
2013-06-12  7:52           ` Vinod Koul
2013-06-12  8:38             ` Andy Shevchenko
2013-06-12  8:12               ` Vinod Koul
2013-06-12  8:53                 ` Viresh Kumar
2013-06-12  8:19                   ` Vinod Koul
2013-06-12  9:06                     ` Viresh Kumar
2013-06-12  9:07                     ` Andy Shevchenko
2013-06-12  9:02                       ` Vinod Koul
2013-06-12  9:43                         ` Viresh Kumar
2013-06-12 11:36                         ` Arnd Bergmann
2013-06-12  9:00                 ` Andy Shevchenko
2013-06-12 13:52                   ` Hein Tibosch
2013-06-05 12:26 ` [PATCH v2 3/4] dma: dw: split driver to library part and platform code Andy Shevchenko
2013-06-05 12:26 ` [PATCH v2 4/4] dma: dw: add PCI part of the driver Andy Shevchenko
2013-06-11 12:39 ` Andy Shevchenko [this message]
2013-06-12  5:17   ` [PATCH v2 0/4] dw_dmac: move to own folder and split 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=1370954397.29283.329.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spear-devel@list.st.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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

Powered by JetHome