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 DAADABD0 for ; Wed, 11 Oct 2017 18:52:10 +0000 (UTC) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 402DD4F0 for ; Wed, 11 Oct 2017 18:52:10 +0000 (UTC) From: Jani Nikula To: James Bottomley , Julia Lawall In-Reply-To: <1507568189.3100.29.camel@HansenPartnership.com> References: <20171005192002.hxbjjdjhrfa4oa37@thunk.org> <1507303665.3104.13.camel@HansenPartnership.com> <1507567045.3100.16.camel@HansenPartnership.com> <1507568189.3100.29.camel@HansenPartnership.com> Date: Wed, 11 Oct 2017 21:51:52 +0300 Message-ID: <871sm9plfb.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 09 Oct 2017, James Bottomley wrote: > On Mon, 2017-10-09 at 18:49 +0200, Julia Lawall wrote: >> Do you suggest one big patch, that goes to who?=C2=A0=C2=A0Or lots of li= ttle >> 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 I'm not particularly thrilled about. I'd much rather see the patches to our driver come through our tree, and we generally deal with them without a fuss. BR, Jani. --=20 Jani Nikula, Intel Open Source Technology Center