All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 DMA40 device tree migration base
Date: Mon, 27 May 2013 20:13:20 -0700	[thread overview]
Message-ID: <20130528031320.GD13532@quad.lixom.net> (raw)
In-Reply-To: <CACRpkdZjr=48_GJxsoYgK7DFUqLs10x4o9yky3MzNR7vh24ogA@mail.gmail.com>

On Thu, May 23, 2013 at 09:34:22PM +0200, Linus Walleij wrote:
> Hi ARM SoC folks,
> 
> here is a patch set that Lee has been chiseling out recently. I've
> accumulated it in my ux500 tree and piled ACKs on the first 36
> patches of the patch set. Basically that includes ACKs from
> subsystem maintainers Vinod Koul and Herbert Xu for affected
> parts.
> 
> We need to get this into Linux-next to proceed with further
> migration on top of it. All have been circulated on the lists for
> a while.
> 
> Please pull this into an apropriate ARM SoC branch for v3.11!
> 
> If we can get ACKs for the rest of the patches in Lee's set these
> will arrive on top of this base as soon as they are ready.
> 
> Yours,
> Linus Walleij
> 
> The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
> 
>   Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
> tags/ux500-dma40-for-arm-soc

Thanks, pulled into next/drivers.

I see the conversions have been made the brute-force way instead of keeping
backwards compatibility and cleaning up drivers before removing no longer
needed board code. That should be fine, as long as you don't introduce too
crazy dependencies (and conflicts) in the code you're talking about adding on
top. 


-Olof

  reply	other threads:[~2013-05-28  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 19:34 [GIT PULL] ux500 DMA40 device tree migration base Linus Walleij
2013-05-28  3:13 ` Olof Johansson [this message]
2013-05-28  9:28   ` Lee Jones

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=20130528031320.GD13532@quad.lixom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.