From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753914AbcCMCIT (ORCPT ); Sat, 12 Mar 2016 21:08:19 -0500 Received: from mail-pf0-f176.google.com ([209.85.192.176]:35120 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753839AbcCMCH4 (ORCPT ); Sat, 12 Mar 2016 21:07:56 -0500 Date: Sat, 12 Mar 2016 16:14:41 -0800 From: Olof Johansson To: Lars Persson Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk, linux-kernel@vger.kernel.org, Lars Persson Subject: Re: [PATCH] ARM: dts: artpec: update clock bindings in artpec6.dtsi Message-ID: <20160313001441.GD17502@localhost> References: <1456392854-13527-1-git-send-email-larper@axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1456392854-13527-1-git-send-email-larper@axis.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 25, 2016 at 10:34:14AM +0100, Lars Persson wrote: > The clock bindings for the main clock controller was changed to an > indexed controller style binding on request of the clk > maintainers. This updates the dtsi to use the new bindings. > > Signed-off-by: Lars Persson > --- > Note: This patch depends on a header file delivered through the clk tree in > "clk: add device tree binding for Artpec-6 clock controller". This is a bit painful for us. It works when we get contents sent as pull requests, since then we can share a branch with the clk header file on it. However, when we apply patches that's harder. I suggest we merge this after both trees have been picked up instead. Please resend after that if we for some reason forget. The alternative is to just use the numerical constants now, and switch to the symbols after the merge window (or in the next release). I'm getting tempted to propose that solution for more and more of these in the future, since it's a somewhat annoying dependency to have (and we often have them). Either way, we're close to the merge window opening, so let's aim to do this patch towards the end. Since it's a new platform, risk for regression doesn't exist, etc. -Olof