From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755180AbaCLPqr (ORCPT ); Wed, 12 Mar 2014 11:46:47 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:38849 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755145AbaCLPqm (ORCPT ); Wed, 12 Mar 2014 11:46:42 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 108.39.110.144 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18YY5YH4Jh98TSfKHMBlJbugAUr+LLaCuo= X-DKIM: OpenDKIM Filter v2.0.1 titan 3663654128F Date: Wed, 12 Mar 2014 11:46:24 -0400 From: Jason Cooper To: Linus Walleij Cc: Sebastian Hesselbarth , Andrew Lunn , Russell King , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Gregory Clement , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 3/3] pinctrl: mvebu: silence WARN to dev_warn Message-ID: <20140312154624.GB7811@titan.lakedaemon.net> References: <1393977790-29110-1-git-send-email-sebastian.hesselbarth@gmail.com> <1393977790-29110-4-git-send-email-sebastian.hesselbarth@gmail.com> <20140306201803.GL1872@titan.lakedaemon.net> <20140307035056.GQ1872@titan.lakedaemon.net> <20140307134616.GR1872@titan.lakedaemon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 12, 2014 at 03:02:02PM +0100, Linus Walleij wrote: > On Fri, Mar 7, 2014 at 2:46 PM, Jason Cooper wrote: > > On Fri, Mar 07, 2014 at 11:56:11AM +0800, Linus Walleij wrote: > > >> For a single patch? > > > > Well, just the doc change and WARN change. I've already taken the dts > > change into mvebu/dt (for arm-soc). > > I've applied this patch [3/3] to the pinctrl tree. Ok, thanks. > > There should be no need for these two to be in mvebu's for-next, so if > > it's easier for you to pick them, please do so. > > > > I'll drop them from mvebu/pinctrl and update mvebu's for-next right now. > > No, I mean, please apply patch 1/3 and 2/3 to the mvebu tree. > There is no need to sync DTS and pinctrl driver changes. This > patch to the pinctrl driver I want to carry however. Sorry I wasn't clear. patch 2/3 depends on 356ca6ce0aa4 devicetree: bindings: update MVEBU pinctrl binding documentation Which is in the mvebu/pinctrl branch you have merged into your tree. I usually keep the binding documentation changes in the same branch with the code changes so that during a future bisect, the documentation has a better chance of being consistent with the code at the point of failure. It's a detail thing, I know, but I couldn't find a downside to doing it. Well, until now. :-) thx, Jason.