linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: dts: vexpress: updates for v4.18
Date: Tue, 15 May 2018 13:47:42 -0700	[thread overview]
Message-ID: <20180515204742.3pptod2a5w6fpawx@localhost> (raw)
In-Reply-To: <20180514162144.GA8409@e107155-lin>

On Mon, May 14, 2018 at 05:21:44PM +0100, Sudeep Holla wrote:
> Hi ARM-SoC team,
> 
> Please pull !
> 
> Note that the commit restructuring motherboard dtsi touches the file
> in ARM64 DT but that's because of the way the file gets included and
> it's not something newly introduced here.
> 
> Regards,
> Sudeep
> 
> --
> 
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> 
>   Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/vexpress-updates-4.18
> 
> for you to fetch changes up to b67b00eeddac0fea494d6339618ffd3da071c2e4:
> 
>   ARM: dts: vexpress: replace '_' with '-' in node names (2018-05-11 14:12:32 +0100)
> 
> ----------------------------------------------------------------
> ARMv7 Vexpress updates/cleanups for v4.18
> 
> 1. 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
> 
> 2. Use of standard GPIO controller bindings for few sysreg components
>    like LED, MMC Write Protect/Card Detect and Flash Write Protect
>    to fix some of the new DTC warnings
> 
> 3. Cleanup to replace all underscores('_') with hyphens('-') in the
>    device node names

Merged, thanks!


-Olof

      reply	other threads:[~2018-05-15 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 16:21 [GIT PULL] ARM: dts: vexpress: updates for v4.18 Sudeep Holla
2018-05-15 20: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=20180515204742.3pptod2a5w6fpawx@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).