Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753823AbcLIMaL (ORCPT ); Fri, 9 Dec 2016 07:30:11 -0500 Received: from mga06.intel.com ([134.134.136.31]:18227 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752625AbcLIMaJ (ORCPT ); Fri, 9 Dec 2016 07:30:09 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,324,1477983600"; d="scan'208";a="200813688" Date: Fri, 9 Dec 2016 14:25:41 +0200 From: Mika Westerberg To: Lee Jones Cc: Marek Vasut , Cyrille Pitchen , Boris Brezillon , Richard Weinberger , Brian Norris , David Woodhouse , Peter Tyser , key.seong.lim@intel.com, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org Subject: Re: [PATCH v6 0/3] spi-nor: Add support for Intel SPI serial flash controller Message-ID: <20161209122541.GN1501@lahna.fi.intel.com> References: <20161128120626.130693-1-mika.westerberg@linux.intel.com> <20161205112727.GI1459@lahna.fi.intel.com> <2dac1535-de7f-47c3-2747-ba8cac854811@gmail.com> <20161205163106.GJ1459@lahna.fi.intel.com> <62db8daa-7ebf-1a42-bd70-897c3c636e3c@atmel.com> <20161206094525.GA25385@dell.home> <20161207085330.GN1459@lahna.fi.intel.com> <0695162f-0959-ab2c-4e68-14881e386060@gmail.com> <20161209085753.GC3625@dell.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161209085753.GC3625@dell.home> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1133 Lines: 27 On Fri, Dec 09, 2016 at 08:57:53AM +0000, Lee Jones wrote: > On Wed, 07 Dec 2016, Marek Vasut wrote: > > > On 12/07/2016 09:53 AM, Mika Westerberg wrote: > > > On Tue, Dec 06, 2016 at 09:45:25AM +0000, Lee Jones wrote: > > >> I'm happy either way. However if you take them, I will require a > > >> pull-request to an immutable branch containing only these patches. > > >> > > >> If I take them, it won't be until v4.11, since we are half way though > > >> -rc8 already and I would like them to soak in -next for at least a > > >> couple of weeks. > > > > > > This series already missed v4.8 and v4.9 so I don't think there is a > > > rush to get it for v4.10 either ;-) I'm fine if it goes for v4.11. > > > > Hmmmmmmmmmmm, that kinda sucks. Lee, are you positive this isn't 4.10 > > material ? > > The merge-window opens in 2 days. > > As I mentioned, I like patches to reside in -next for at least 1 maybe > 2 RC cycles before merging. It's far to easy to accept code, then get > bitten if/when it breaks after being merged by Linus. I agree. Better to give it some time in linux-next. Can you queue this series for v4.11?