From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: dts: vexpress/juno: Updates for v4.6(part 2)
Date: Sat, 12 Mar 2016 17:26:31 -0800 [thread overview]
Message-ID: <20160313012631.GA5883@localhost> (raw)
In-Reply-To: <56DF0274.1060007@arm.com>
On Tue, Mar 08, 2016 at 04:48:52PM +0000, Sudeep Holla wrote:
> Hi ARM-SoC team,
>
> Sorry for the late pull request.
>
> There's one update for adding support for SBSA Watchdog to foundation
> model that caused conflict as it was merged via watchdog tree. I am
> pulling that now to avoid conflicts and I also have a patch to fix DT
> warnings that new checks in DTS introduced since last Friday. Please
> consider pulling this for v4.6
>
> Regards,
> Sudeep
>
>
> The following changes since commit 9fd9288ed0899f9e318a97d73e777d6d3357265e:
>
> arm64: dts: Add HDLCD support on Juno platforms (2016-02-10 10:58:33
> +0000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
> tags/vexpress-for-v4.6/dt-updates-2
>
> for you to fetch changes up to 6d6acd140ab3d46348ec3a9dbfd386d9ca42b825:
>
> arm64: dts: juno/vexpress: fix node name unit-address presence warnings
> (2016-03-08 13:54:27 +0000)
>
> ----------------------------------------------------------------
> Additional updates for ARM VExpress/Juno platforms
>
> 1. Add support for SBSA Generic Watchdog on foundation models
>
> 2. Fix node name unit-address presence/absence mismatch warnings in
> all the device trees
Argh. I just noticed that I had mismerged your previos patch into next/dt
instead of next/dt64. So, I've merged this on top of it there as well.
-Olof
prev parent reply other threads:[~2016-03-13 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 16:48 [GIT PULL] arm64: dts: vexpress/juno: Updates for v4.6(part 2) Sudeep Holla
2016-03-13 1:20 ` Olof Johansson
2016-03-13 1:26 ` 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=20160313012631.GA5883@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.