From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D98C7AAC for ; Mon, 16 Oct 2017 18:37:38 +0000 (UTC) Received: from smtprelay.hostedemail.com (smtprelay0190.hostedemail.com [216.40.44.190]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F02CC4D4 for ; Mon, 16 Oct 2017 18:37:37 +0000 (UTC) Received: from smtprelay.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by smtpgrave03.hostedemail.com (Postfix) with ESMTP id E8C5018014D2F for ; Mon, 16 Oct 2017 16:07:42 +0000 (UTC) Message-ID: <1508170057.6530.13.camel@perches.com> From: Joe Perches To: Jani Nikula , James Bottomley , Julia Lawall Date: Mon, 16 Oct 2017 09:07:37 -0700 In-Reply-To: <8760bfmaoz.fsf@intel.com> References: <20171005192002.hxbjjdjhrfa4oa37@thunk.org> <1507303665.3104.13.camel@HansenPartnership.com> <1507567045.3100.16.camel@HansenPartnership.com> <1507568189.3100.29.camel@HansenPartnership.com> <871sm9plfb.fsf@intel.com> <1508163175.7571.2.camel@HansenPartnership.com> <8760bfmaoz.fsf@intel.com> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2017-10-16 at 17:25 +0300, Jani Nikula wrote: > On Mon, 16 Oct 2017, James Bottomley wrote: > > On Wed, 2017-10-11 at 21:51 +0300, Jani Nikula wrote: > > > On Mon, 09 Oct 2017, James Bottomley > > ip.com> wrote: > > > > > > > > On Mon, 2017-10-09 at 18:49 +0200, Julia Lawall wrote: > > > > > > > > > > Do you suggest one big patch, that goes to who?  Or lots of > > > > > little > > > > > patches that go out at once to the individual maintainers of the > > > > > affected code? > > > > > > > > I was actually thinking we validate the script and if there are no > > > > problems, apply it at -rc1 ... so effectively one big patch. > > > > > > By -rc1 we (drm in general, drm/i915 in particular) will already have > > > accumulated easily 4-5 weeks' worth of commits for the *next* merge > > > window. Applying treewide stuff to Linus' tree at -rc1 forces a > > > backmerge and potentially conflicts galore > > > > If we're applying a semantic patch script (and we've verified it works > > well enough to use the script on the -rc1 main tree), couldn't you > > simply apply it to your tree at the same time? > > If we did, the fixes would show up in a later kernel release. Which is > just fine for us. In other words, just let subsystems and drivers handle > this as they see fit? Scheduling and acceptance rates are the issue. Also some scripted patches require complete treewide application to allow things like API changes.