From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: dts: juno: updates for v4.18
Date: Tue, 15 May 2018 13:48:21 -0700 [thread overview]
Message-ID: <20180515204821.qxdnwl5u3rndg7if@localhost> (raw)
In-Reply-To: <20180514162317.GB8409@e107155-lin>
On Mon, May 14, 2018 at 05:23:17PM +0100, Sudeep Holla wrote:
> Hi ARM-SoC team,
>
> Please pull !
>
> Note that the tag is based on v4.17-rc3 instead of -rc1 as a fix went in
> -rc3 and conflicts with changes here. The conflicts themselves are
> trivial and hence I can based the change on -rc1 if required.
>
> Regards,
> Sudeep
>
> --
>
> The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64:
>
> Linux v4.17-rc3 (2018-04-29 14:17:42 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/juno-updates-4.18
>
> for you to fetch changes up to 349b0f95e1ea718d912ca6875a40813e52a4ba39:
>
> arm64: dts: juno/rtsm: re-structure motherboard includes (2018-05-10 11:01:56 +0100)
>
> ----------------------------------------------------------------
> ARMv8 Juno/Vexpress updates/cleanups for v4.18
>
> 1. Add the missing connections to the STM output port as all endpoint
> connections must be bidirectional.
>
> 2. Replace all the custom OF graph endpoint node names with the standard
> 'endpoint'
>
> 3. Cleanup to replace all underscores('_') with hyphens('-') in the
> device node names
>
> 4. Syntactic restructuring of motherboard include file so that it can be
> included at the top of any other DTS file as it should be rather than
> existing include in the middle of the file at a specific location
Merged, thanks!
-Olof
prev parent reply other threads:[~2018-05-15 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 16:23 [GIT PULL] arm64: dts: juno: updates for v4.18 Sudeep Holla
2018-05-15 20:48 ` 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=20180515204821.qxdnwl5u3rndg7if@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).