From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/6] omap device tree changes for v3.13 merge window
Date: Mon, 14 Oct 2013 15:36:54 -0700 [thread overview]
Message-ID: <87eh7n4gzd.fsf@linaro.org> (raw)
In-Reply-To: <5258a9a8.493e310a.779b.1b15SMTPIN_ADDED_MISSING@mx.google.com> (Tony Lindgren's message of "Fri, 11 Oct 2013 18:44:58 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:
>
> Linux 3.12-rc4 (2013-10-06 14:00:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/dt-signed
>
> for you to fetch changes up to c49f4984fd45be36502e903e7a5a6a4faff42931:
>
> Merge tag 'for_3.13/dts_signed' of git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt into omap-for-v3.13/dt (2013-10-11 15:40:07 -0700)
>
> ----------------------------------------------------------------
>
> omap device tree related changes via Benoit Cousson <bcousson@baylibre.com>:
>
> Add the minimal DTS support for DRA7xx based SoC core.
> Add the initial support for N900 and gta04 phones.
> Enable USB3 on OMAP5 evm board.
> Add support for cryto accelerators
> Add new IGEP AQUILA board
> Add AM33XX EDMA support
> Update HSUSB node to use the reset-gpios fmwk
Thanks, pulled into next/dt.
Kevin
next parent reply other threads:[~2013-10-14 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5258a9a8.493e310a.779b.1b15SMTPIN_ADDED_MISSING@mx.google.com>
2013-10-14 22:36 ` Kevin Hilman [this message]
2013-10-12 1:44 [GIT PULL 1/6] omap non-urgent fixes for v3.13 merge window Tony Lindgren
2013-10-12 1:44 ` [GIT PULL 4/6] omap device tree changes " Tony Lindgren
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=87eh7n4gzd.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).