From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] device tree updates for omaps for v4.8 merge window
Date: Mon, 4 Jul 2016 21:47:57 -0700 [thread overview]
Message-ID: <20160705044757.GL1669@localhost> (raw)
In-Reply-To: <20160622110640.GD22353@atomide.com>
Hi,
On Wed, Jun 22, 2016 at 04:06:42AM -0700, Tony Lindgren wrote:
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.8/dt-part1-signed-v2
>
> for you to fetch changes up to 52c7c91319e469142628199548852198bcc3150f:
>
> ARM: dts: AM43xx: Add node for RNG (2016-06-22 00:44:16 -0700)
>
> ----------------------------------------------------------------
> Device tree changes for omaps for v4.8 merge window:
>
> - PWM binding updates and related dts changes
>
> - OCM RAM updates for dra7
>
> - Enable n900 lirc-rx51 driver
>
> - omap3-gta04 updates for backlight, bma180, itg3200, hmc5843 and wifi
>
> - am335x, am437x and am57xx operating point updates and additions
>
> - am335x-icev2 pca9536 node
>
> - dra72-evm regulator updates
>
> - edma spelling fixes
>
> - am335x and am437x ethernet phy update
>
> - a series of mcbsp updates
>
> - omap3-gta04 eeprom
>
> - dra7 PCIe unit address fix
>
> - stdout-path for beaglebone variants
>
> - crypto accelerator nodes for am335x, am437x and dra7
Merged, thanks.
-Olof
prev parent reply other threads:[~2016-07-05 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:06 [GIT PULL] device tree updates for omaps for v4.8 merge window Tony Lindgren
2016-07-05 4:47 ` Olof Johansson [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=20160705044757.GL1669@localhost \
--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 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).