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 B0036E7E for ; Tue, 11 Sep 2018 17:12:56 +0000 (UTC) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 42A877D3 for ; Tue, 11 Sep 2018 17:12:56 +0000 (UTC) From: Jani Nikula To: Guenter Roeck , Mark Brown In-Reply-To: <20180911170212.GC8284@roeck-us.net> References: <20180907004944.GD16300@sasha-vm> <20180907014930.GE16300@sasha-vm> <20180907145437.GF16300@sasha-vm> <20180910194310.GV16300@sasha-vm> <20180910164519.6cbcc116@vmware.local.home> <20180910212019.GA32269@roeck-us.net> <20180911111853.GB8018@sirena.org.uk> <20180911170212.GC8284@roeck-us.net> Date: Tue, 11 Sep 2018 20:12:37 +0300 Message-ID: <87k1nsdkl6.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug-introducing patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 11 Sep 2018, Guenter Roeck wrote: > FWIW, for the most part I stopped reporting issues with -next after some people > yelled at me for the 'noise' I was creating. Along the line of "This has been > fixed in branch xxx; why don't you do your homework and check there", with > branch xxx not even being in -next. What would be the reason for *not* having all the branches, including fixes, of a subsystem/driver in linux-next? Baffled. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center