Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754401AbbBFB70 (ORCPT ); Thu, 5 Feb 2015 20:59:26 -0500 Received: from mail-pa0-f43.google.com ([209.85.220.43]:56669 "EHLO mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752782AbbBFB7Y (ORCPT ); Thu, 5 Feb 2015 20:59:24 -0500 Date: Thu, 5 Feb 2015 17:59:17 -0800 From: Brian Norris To: Lee Jones Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, kernel@stlinux.com, devicetree@vger.kernel.org, Rob Herring , Mark Rutland Subject: Re: [PATCH v3 00/13] mtd: st_spi_fsm: Align with ST's internal development Message-ID: <20150206015917.GA18140@ld-irv-0074> References: <1418644760-18773-1-git-send-email-lee.jones@linaro.org> <20150113051452.GR9759@ld-irv-0074> <20150121124930.GA22024@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150121124930.GA22024@x1> 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: 929 Lines: 21 On Wed, Jan 21, 2015 at 12:49:30PM +0000, Lee Jones wrote: > On Mon, 12 Jan 2015, Brian Norris wrote: > > Typically "simpler" and "reducing the cost of having lots of extra DT > > properties" aren't good enough reasons for immediately breaking an > > existing DT binding. We usually expect to support both for some period > > of time. > > Only once a binding has became ABI. As there are no users of this > driver yet (this will change after this sync'ing patch-set has been > applied), so we can safely consider this binding to be in-progress and > as such, not yet ABI, thus we can do this ol' switch-aroo without the > usual 6 month deprecation period. OK, fine with me. Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/