From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH 1/3] ARM: dts: Create a cros-ec-keyboard fragment Date: Thu, 05 Jun 2014 09:51:53 -0600 Message-ID: <53909219.6090200@wwwdotorg.org> References: <1401920421-25729-1-git-send-email-dianders@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1401920421-25729-1-git-send-email-dianders@chromium.org> Sender: linux-kernel-owner@vger.kernel.org To: Doug Anderson , olof@lixom.net, "arm@kernel.org" Cc: Stephen Warren , Thierry Reding , Kukjin Kim , Tomasz Figa , mark.rutland@arm.com, devicetree@vger.kernel.org, linux@arm.linux.org.uk, pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org, robh+dt@kernel.org, galak@codeaurora.org, Javier Martinez Canillas , linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org On 06/04/2014 04:20 PM, Doug Anderson wrote: > All ChromeOS ARM devices that have the standard "CrOS EC" have the > same keyboard mapping. It's silly to include this same definition > everywhere. Let's create a "dtsi" fragment that we can include from > many different boards. > > This fragment is based on what's currently in tegra124-venice2.dts This series looks fine to me. Given it touches both Tegra and Exynos, should it be merged into a topic branch in arm-soc, so that it can be pulled into both Tegra/Exynos trees to resolve any conflicts. So, Acked-by: Stephen Warren If you want, I'm happy to apply this to a topic branch and send a pull request to arm-soc.