From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: dts: TI AM65x changes for 4.20
Date: Sun, 23 Sep 2018 06:32:08 -0700 [thread overview]
Message-ID: <20180923133208.zwuxw5jpjq24afm3@localhost> (raw)
In-Reply-To: <404ebcc1-7e8c-c505-a6ac-10a94f6bd608@ti.com>
On Wed, Sep 19, 2018 at 09:54:08PM +0300, Tero Kristo wrote:
> Hi ARM-SoC team,
>
> Here are the TI AM65x DTS changes towards 4.20 merge window. Applied on top
> of 4.19-rc2 basically just because of some testing considerations, please
> let me know if that is not fine.
No worries - next/dt is already on -rc2 in this case. If in doubt, see what our
for-next has as a base at the time. In general rc1-3 are fair game. Beyond
that, it's on a case by case basis and ask if you're uncertain.
>
> The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
>
> Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux
> tags/am654-for-v4.20
>
> for you to fetch changes up to 42e54f6467ecc25f464d74c0fcea0c9fab1c2e3b:
>
> arm64: dts: ti: k3-am6: Add Device Management Security Controller support
> (2018-09-18 18:25:06 +0300)
>
> ----------------------------------------------------------------
> TI AM654 support for v4.20 merge window.
>
> This branch adds changes for the Texas Instruments AM654 SoC. Included
> changes are:
> - Add uart nodes
> - Change address cells and size-cells of interconnect tfrom 1 to 2
> - Add secure proxy instance for main domain
> - Add DMSC support
Merged, thanks!
-Olof
prev parent reply other threads:[~2018-09-23 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 18:54 [GIT PULL] arm64: dts: TI AM65x changes for 4.20 Tero Kristo
2018-09-23 13:32 ` 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=20180923133208.zwuxw5jpjq24afm3@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