linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ste_dma40 updates for 3.9
Date: Mon, 14 Jan 2013 22:48:15 -0800	[thread overview]
Message-ID: <CAOesGMg6FqsaqZiGeK14n4==dF-y=iMYSGRDBYSwkGWO0J69Yg@mail.gmail.com> (raw)
In-Reply-To: <20130114101542.GA5363@balto.lan>

Hi,

On Mon, Jan 14, 2013 at 2:15 AM, Fabio Baltieri
<fabio.baltieri@linaro.org> wrote:
> Hello Arnd, Olof,
>
> 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?


Thanks,

-Olof

  reply	other threads:[~2013-01-15  6:48 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 [this message]
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
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='CAOesGMg6FqsaqZiGeK14n4==dF-y=iMYSGRDBYSwkGWO0J69Yg@mail.gmail.com' \
    --to=olof@lixom.net \
    --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).