linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: DT changes for v3.14 (set #2)
Date: Tue, 10 Dec 2013 09:29:10 -0800	[thread overview]
Message-ID: <878uvs8vix.fsf@linaro.org> (raw)
In-Reply-To: <20131208003236.GD11251@titan.lakedaemon.net> (Jason Cooper's message of "Sat, 7 Dec 2013 19:32:36 -0500")

Jason Cooper <jason@lakedaemon.net> writes:

> Guys,
>
> Nothing big here, Arnaud's been busy wit hthe Netgear boards ;-)
>
> In -next for 5 days or so.
>
> This is an incremental pull, from tags/mvebu-dt-3.14 in mvebu/dt branch.
> Olof pulled the first set into arm-soc/cleanup, so this branch will
> depend upon that.

Looks like the first set of your DT changes is in next/dt (not our
cleanup branch) so I pulled this into next/dt as well.

Kevin

      reply	other threads:[~2013-12-10 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08  0:32 [GIT PULL] ARM: mvebu: DT changes for v3.14 (set #2) Jason Cooper
2013-12-10 17:29 ` Kevin Hilman [this message]

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=878uvs8vix.fsf@linaro.org \
    --to=khilman@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).