From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/7] Broadcom devicetree-arm64 changes for 4.12
Date: Fri, 31 Mar 2017 11:53:17 +0200 [thread overview]
Message-ID: <CAK8P3a2_DFkmf76OmES4422sfUnti8G33dB6db4jG=X7Kv2_PQ@mail.gmail.com> (raw)
In-Reply-To: <20170324175807.27272-3-f.fainelli@gmail.com>
On Fri, Mar 24, 2017 at 6:58 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM64-based SoCs Device Tree updates for
> 4.12, please pull the following:
>
> - Rob enables the cryptographic block on Northstar 2 (SPU) by adding the proper
> Device Tree nodes
>
> - Jon replaces all occurences of: status = "ok" with status = "okay" to better
> conform to the Device Tree specification
Pulled into next/dt64, thanks!
Arnd
next prev parent reply other threads:[~2017-03-31 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 17:58 [GIT PULL 1/7] Broadcom soc changes for 4.12 Florian Fainelli
2017-03-24 17:58 ` [GIT PULL 2/7] Broadcom devicetree " Florian Fainelli
2017-03-25 21:33 ` Baruch Siach
2017-03-27 17:14 ` Eric Anholt
2017-03-27 19:52 ` Florian Fainelli
2017-03-31 10:04 ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 3/7] Broadcom devicetree-arm64 " Florian Fainelli
2017-03-31 9:53 ` Arnd Bergmann [this message]
2017-03-24 17:58 ` [GIT PULL 4/7] Broadcom maintainers " Florian Fainelli
2017-03-31 8:56 ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 5/7] Broadcom defconfig " Florian Fainelli
2017-03-31 9:01 ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 6/7] Broadcom defconfig-arm64 " Florian Fainelli
2017-03-31 9:04 ` Arnd Bergmann
2017-03-24 17:58 ` [GIT PULL 7/7] Broadcom drivers " Florian Fainelli
2017-03-31 8:59 ` Arnd Bergmann
2017-03-30 15:29 ` [GIT PULL 1/7] Broadcom soc " Arnd Bergmann
2017-03-31 8:53 ` Arnd Bergmann
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='CAK8P3a2_DFkmf76OmES4422sfUnti8G33dB6db4jG=X7Kv2_PQ@mail.gmail.com' \
--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;
as well as URLs for NNTP newsgroup(s).