From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap device tree changes for v4.7 merge window, part 1
Date: Sun, 24 Apr 2016 23:51:11 +0200 [thread overview]
Message-ID: <13923085.h5mVoITCv7@wuerfel> (raw)
In-Reply-To: <20160422223829.GO5995@atomide.com>
On Friday 22 April 2016 15:38:29 Tony Lindgren wrote:
> First set of device tree changes for omaps for v4.7 merge window:
>
> - Two sets of name and unit address check fixes for dts files.
>
> - DMA, McASP, and timer and regulator related dts changes for dra7
>
> - Add more devices for Nokia N9/N950
>
> - Initial support for am335x ICEv2
>
> - Initial support for am572x-IDK
>
> - Pinctrl changes for am335x-baltos-ir5221
>
> - Initial support for Amazon Kindle Fire (first generation)
>
> - A series of changes to add GPIO controller support for the
> GPMC driver. The driver changes will be merged separately.
>
> - Support for am43xx clkout1
>
> - Pinctrl and RTC changes for am335x-chili
>
> - Add support for dra72-evm rev C (SR2.0)
>
Pulled into next/dt, thanks!
Arnd
prev parent reply other threads:[~2016-04-24 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 22:38 [GIT PULL] omap device tree changes for v4.7 merge window, part 1 Tony Lindgren
2016-04-24 21:51 ` Arnd Bergmann [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=13923085.h5mVoITCv7@wuerfel \
--to=arnd@arndb.de \
--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