From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] arm64: Juno DT updates and new DT for Juno R1
Date: Mon, 18 May 2015 22:14:23 +0200 [thread overview]
Message-ID: <4136868.8yCICAPH00@wuerfel> (raw)
In-Reply-To: <1431970109-8902-1-git-send-email-Liviu.Dudau@arm.com>
On Monday 18 May 2015 18:28:24 Liviu Dudau wrote:
> This series restructures the Juno DT files and introduces the DT
> for the new Juno R1. The board is an update of the Juno R0 with
> support for PCIe, but the current series only brings the board to
> parity with Juno R0. The series that enable the PCIe Generic Host
> Bridge to be used on Juno R1 will be posted separately.
>
> Changes from v1:
> - Moved memory node inside juno-base.dtsi as this is common between
> boards and unlikely to change soon.
> - Added "arm,juno-r1" as compatible string in juno-r1.dts at Jon Medhurst's
> suggestion.
Are you planning to send a pull request to arm at kernel.org for this when
you're happy with the state, or should we pick up the patches from the
list?
Arnd
next prev parent reply other threads:[~2015-05-18 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 17:28 [PATCH v2 0/5] arm64: Juno DT updates and new DT for Juno R1 Liviu Dudau
2015-05-18 17:28 ` [PATCH v2 1/5] arm64: Juno: Fix the GIC node address label and the frequency of FAXI clock Liviu Dudau
2015-05-18 17:28 ` [PATCH v2 2/5] arm64: Juno: Split juno.dts into juno-base.dtsi and juno.dts Liviu Dudau
2015-05-18 17:28 ` [PATCH v2 3/5] arm64: Juno: Add memory mapped timer node Liviu Dudau
2015-05-19 10:56 ` Jon Medhurst (Tixy)
2015-05-19 11:31 ` Liviu Dudau
2015-05-19 12:58 ` Jon Medhurst (Tixy)
2015-05-18 17:28 ` [PATCH v2 4/5] arm64: Juno: Add GICv2m support in device tree Liviu Dudau
2015-05-18 17:28 ` [PATCH v2 5/5] arm64: Add DT support for Juno r1 board Liviu Dudau
2015-05-18 20:14 ` Arnd Bergmann [this message]
2015-05-18 22:31 ` [PATCH v2 0/5] arm64: Juno DT updates and new DT for Juno R1 Liviu Dudau
2015-05-19 11:11 ` Sudeep Holla
2015-05-20 10:47 ` Liviu Dudau
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=4136868.8yCICAPH00@wuerfel \
--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).