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 (incr #3)
Date: Thu, 19 Dec 2013 07:37:36 -0800	[thread overview]
Message-ID: <8738lolum7.fsf@linaro.org> (raw)
In-Reply-To: <20131214222139.GG2609@titan.lakedaemon.net> (Jason Cooper's message of "Sat, 14 Dec 2013 17:21:39 -0500")

Jason Cooper <jason@lakedaemon.net> writes:

> Guys,
>
> Here's another round of DT changes.  They've all been in -next for at
> least a few days.  This is an incremental pull from tags/mvebu-dt-3.14-2
> in the mvebu/dt branch.
>
> thx,
>
> Jason.
>
>
> The following changes since commit 46ca506c43d64e11257a0a113701e9bcccf52416:
>
>   ARM: kirkwood: Add support for NETGEAR ReadyNAS NV+ v2 (2013-12-01 22:18:44 +0000)
>
> are available in the git repository at:
>
>   git://git.infradead.org/linux-mvebu.git tags/mvebu-dt-3.14-3
>
> for you to fetch changes up to 69e18e26b5773092276a9702244784faf9b6c65f:
>
>   ARM: mvebu: Enable NAND controller in A370 Reference Design board (2013-12-12 14:04:34 +0000)
>
> ----------------------------------------------------------------
> mvebu DT changes for v3.14 (incr. #3)
>
>  - kirkwood
>     - use symbolic names for gpios and key inputs
>
>  - mvebu
>     - add the pxa nand controller to the ReadyNAS and A370-RD boards
>
> ----------------------------------------------------------------

Pulled into next/dt.

Thanks,

Kevin

      reply	other threads:[~2013-12-19 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 22:21 [GIT PULL] ARM: mvebu: DT changes for v3.14 (incr #3) Jason Cooper
2013-12-19 15:37 ` 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=8738lolum7.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).