From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932703AbbERUOg (ORCPT ); Mon, 18 May 2015 16:14:36 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:49335 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932302AbbERUOd (ORCPT ); Mon, 18 May 2015 16:14:33 -0400 From: Arnd Bergmann To: Liviu Dudau Cc: Olof Johansson , Rob Herring , "Jon Medhurst (Tixy)" , Mark Rutland , Ian Campbell , Marc Zyngier , Catalin Marinas , Will Deacon , Sudeep Holla , devicetree , LAKML , LKML Subject: Re: [PATCH v2 0/5] arm64: Juno DT updates and new DT for Juno R1 Date: Mon, 18 May 2015 22:14:23 +0200 Message-ID: <4136868.8yCICAPH00@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1431970109-8902-1-git-send-email-Liviu.Dudau@arm.com> References: <1431970109-8902-1-git-send-email-Liviu.Dudau@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:9PTdKHtRqFKtEkhCDsmJvEvFTL02VTPJz+M+mr3BpBO7StN5P15 8ZqdJk1EEZtOtjlJF38Z2z4bPqpUtjR2m9T0vROFQ0PRJfJazfFF/VFzqHGdH8A/OhrMw6e Om3VyyXrjwQAI+LU2FmWMPa2+6ZZomcMoEHtdC+uRJvt3OidZ41uTwJc25ppaGiH/4qI+qK L7knsMv/xlJ9DX95YMugA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@kernel.org for this when you're happy with the state, or should we pick up the patches from the list? Arnd