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 6AFF6BA9 for ; Wed, 26 Apr 2017 15:25:47 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6CF691A4 for ; Wed, 26 Apr 2017 15:25:46 +0000 (UTC) In-Reply-To: <1493218957.2632.1.camel@sandisk.com> References: <20188905.kHbMkj7sB6@avalon> <1834084.5qZ8rLimvk@avalon> <1492631703.3217.30.camel@HansenPartnership.com> <3f55980c-1e8d-c841-2555-472ed10eb2fc@sandisk.com> <20170426084253.yvxyzb3khh2fej4j@mwanda> <1493218957.2632.1.camel@sandisk.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: James Bottomley Date: Wed, 26 Apr 2017 11:25:12 -0400 To: Bart Van Assche , "dan.carpenter@oracle.com" Message-ID: Cc: "ksummit-discuss@lists.linuxfoundation.org" , "airlied@linux.ie" , "gregkh@linuxfoundation.org" , "mingo@kernel.org" , "dledford@redhat.com" , "davem@davemloft.net" Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On April 26, 2017 11:02:39 AM EDT, Bart Van Assche wrote: >On Wed, 2017-04-26 at 11:42 +0300, Dan Carpenter wrote: >> It's Ok to wait weeks. Months is not OK. >> >> If maintainers are not reading their email then you can try >forwarding >> the patches through Andrew. >> >> I feel like I haven't had such a huge problem with this recently... >Are >> we talking about other arches besides x86 and ARM? My patches are >> normally simple is probably part of the difference. > >Hello Dan, > >In my e-mail I was referring to the code under drivers/target and >drivers/md/dm*. With all due respect, I don't think that Andrew is >familiar >enough with these code bases to accept patches for these subsystems. I think what Dan is referring to is that Andrew used to have an override the maintainer role. He'd take a patch and send out the usual email forcing a nak if it shouldn't go upstream. I.e forcing at least a response. You don't need more than a mechanical review to do this because you're challenging the maintainer to respond. James >Bart. >_______________________________________________ >Ksummit-discuss mailing list >Ksummit-discuss@lists.linuxfoundation.org >https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss -- Sent from my Android device with K-9 Mail. Please excuse my brevity.