linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: fabio.baltieri@linaro.org (Fabio Baltieri)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ste_dma40 updates for 3.9
Date: Tue, 15 Jan 2013 09:55:00 +0100	[thread overview]
Message-ID: <20130115085500.GA18406@balto.lan> (raw)
In-Reply-To: <CAOesGMg6FqsaqZiGeK14n4==dF-y=iMYSGRDBYSwkGWO0J69Yg@mail.gmail.com>

Hello Olof,

On Mon, Jan 14, 2013 at 10:48:15PM -0800, Olof Johansson wrote:
> > This contains a series of updates and fixes for the ste_dma40 driver.
> >
> > The driver is specific for the ux500, and the patches were acked by both Linus
> > Walleij, and Vinod Koul (dmaengine), who agreed to push this through arm-soc.
> >
> > Can you please pull those in for -next?
> 
> While I don't mind taking this through arm-soc, I don't see a strong
> reason to do so?
> 
> This series of patches only modify the ste_dma40 driver, there are no
> corresponding changes under arch/arm that need to be coordinated or
> considered w.r.t. merge conflicts. I.e. they all seem nicely isolated
> to only the driver.
> 
> So is there a specific reason for why these shouldn't just go in
> through the dmaengine tree?

The idea was to have this in the same tree as other ux500 specific
driver patches to easy up testing a bit, but now that you point it out
I see that current arm-soc tree is pretty clear of driver patches (mmci
was what I had in mind) and those should end up to other trees anyway,
so you're probably right and these should go in dmaengine tree.

Vinod, would you please consider pulling these into dmaengine's next
tree?

Thanks,
Fabio

-- 
Fabio Baltieri

  parent reply	other threads:[~2013-01-15  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 10:15 [GIT PULL] ste_dma40 updates for 3.9 Fabio Baltieri
2013-01-15  6:48 ` Olof Johansson
2013-01-15  8:53   ` Linus Walleij
2013-01-15 19:14     ` Olof Johansson
2013-01-20 14:07       ` Vinod Koul
2013-01-21  8:36         ` Fabio Baltieri
2013-01-15  8:55   ` Fabio Baltieri [this message]
2013-01-21 15:10     ` 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=20130115085500.GA18406@balto.lan \
    --to=fabio.baltieri@linaro.org \
    --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).