From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932865AbcFCNFT (ORCPT ); Fri, 3 Jun 2016 09:05:19 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:38295 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932485AbcFCNFQ (ORCPT ); Fri, 3 Jun 2016 09:05:16 -0400 Date: Fri, 3 Jun 2016 14:05:12 +0100 From: Peter Griffin To: Mark Brown Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, srinivas.kandagatla@gmail.com, maxime.coquelin@st.com, patrice.chotard@st.com, vinod.koul@intel.com, ohad@wizery.com, bjorn.andersson@linaro.org, arnd@arndb.de, lee.jones@linaro.org, devicetree@vger.kernel.org, dmaengine@vger.kernel.org, linux-remoteproc@vger.kernel.org, arnaud.pouliquen@st.com Subject: Re: [PATCH v4 10/18] ASoC: sti: Update DT example to match the driver code Message-ID: <20160603130512.GF9912@griffinp-ThinkPad-X1-Carbon-2nd> References: <1464192412-16386-1-git-send-email-peter.griffin@linaro.org> <1464192412-16386-12-git-send-email-peter.griffin@linaro.org> <20160527171403.GN16172@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160527171403.GN16172@sirena.org.uk> 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 Hi Mark, On Fri, 27 May 2016, Mark Brown wrote: > On Wed, May 25, 2016 at 05:06:44PM +0100, Peter Griffin wrote: > > uniperiph-id, version and mode are ST specific bindings and > > need the 'st,' prefix. Update the examples, as otherwise copying > > them yields a runtime error parsing the DT node. > > You've not copied me on the rest of the series so I've no idea what's > going on with dependencies. When sending a patch series it is important > to ensure that all the various maintainers understand what the > relationship between the patches as the expecation is that there will be > interdependencies. Either copy everyone on the whole series or at least > copy them on the cover letter and explain what's going on. If there are > no strong interdependencies then it's generally simplest to just send > the patches separately to avoid any possible confusion. Ok will bare this in mind for v5 series. Regards, Peter.