Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761701AbcJSU3K (ORCPT ); Wed, 19 Oct 2016 16:29:10 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:47069 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761190AbcJSU3H (ORCPT ); Wed, 19 Oct 2016 16:29:07 -0400 DMARC-Filter: OpenDMARC Filter v1.3.1 smtp.codeaurora.org A41D36034D Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=pass smtp.mailfrom=sboyd@codeaurora.org Date: Wed, 19 Oct 2016 13:29:04 -0700 From: Stephen Boyd To: Gabriel Fernandez Cc: Rob Herring , Mark Rutland , Russell King , Maxime Coquelin , Alexandre Torgue , Michael Turquette , Nicolas Pitre , Arnd Bergmann , daniel.thompson@linaro.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, ludovic.barre@st.com, olivier.bideau@st.com, amelie.delaunay@st.com Subject: Re: [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks Message-ID: <20161019202904.GB8871@codeaurora.org> References: <1476436699-21879-1-git-send-email-gabriel.fernandez@st.com> <20161018235108.GP8871@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1427 Lines: 42 On 10/19, Gabriel Fernandez wrote: > Hi Stephen, > > > On 10/19/2016 01:51 AM, Stephen Boyd wrote: > >On 10/14, gabriel.fernandez@st.com wrote: > >>Gabriel Fernandez (6): > >> clk: stm32f4: Add LSI & LSE clocks > >> ARM: dts: stm32f429: add LSI and LSE clocks > >> arm: stmf32: Enable SYSCON > >> clk: stm32f4: Add RTC clock > >> clk: stm32f469: Add QSPI clock > >> ARM: dts: stm32f429: Add QSPI clock > >Can the clk patches be picked without causing problems for > >existing dt changes? Do you want an ack from clk maintainers > >instead of us picking the clk patches up? The series has > >intermingled clk and dts changes so I'm confused. > > > > Thanks for reviewing. > > Normally DT patches will be taken by STM32 maintainer, but yes there > is a dependency between patch 1 & 2, so if you push the patch 1 into > clk-next tree you have to take also patch 2. Let's break the dependency by making the required property optional or key off a different compatible string. As it stands right now applying patch 1 will cause things to break until the second patch lands which is not great. > > You have to be synchronized with Alexandre Torgue. > > I'd prefer zero synchronization. Please just send the clk patches the next time and leave the stuff for arm-soc out of the patch series. Thanks. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project