From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id DE133A04E6; Wed, 18 Nov 2020 10:15:15 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4F77B592C; Wed, 18 Nov 2020 10:15:13 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id EB8D858C4 for ; Wed, 18 Nov 2020 10:15:11 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 7D8781190; Wed, 18 Nov 2020 04:15:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 18 Nov 2020 04:15:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 6t7uSmq6YbuknLdFr4ta0NrEX6D87ry/nc8BcWwx9po=; b=a73jx9qxzkUYAKP0 aPl55bz6IPOv/kEv10J6HI7ios3HtaS0PqZfchmk65Ta+6UimaXNS8yPUbNTJ+gJ 89YyqU3wVj57wN4myBB4mRioP8kk6iHD+7rkyO0ctQWY2pQfWQk95xgHCy1kqzm0 3L7uEpE08TnLAi4+4sUw/YGzIbtkFhWrLqUGq4rFHCj+dMXr/qnjH3HYJtu15lVd W99l5d/xGEwdBWoX/x3A+AYNF62L4n1uP31CEdol5mapSeo19tsMtgVjuSphSUwm Xi+jfcgPFqf4Qx4+ebS3Z+zxeck5+gJOP4mibCBdYKdJkBbZAZtmo+awbKlarfzw VQ5x2w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=6t7uSmq6YbuknLdFr4ta0NrEX6D87ry/nc8BcWwx9 po=; b=meqjj3r0nIQt3dtXUNq2zqO2GcOr32iE+ljzVWbUda8kNaFKvB29MhpDq 8x4Wlh+BxW3Xk/BIK8vSlk8jBSaZPbCIfVUNn2L9mxuuzIjVXYAF0Tjt7eCXOjOZ hrkpUESg1pqvZw/M7Hq83qsPpP+Wv7WNLEih6Fr7R5ABUT0a+8jYq1oQsfwzHCLa pculVaiWOcpQhocPp9tSeHHG3N3fGELMsE6OHRaLhKfTBLr55+iTa2Aw3E591RWN jJdCgqaa5xVVPcAvKGTxibqesphSmZcTLMSkMmIB3CpApFDcv5TfcAw08AFrw6NP BxcTHHjWBxYmjDarluN+F3nbE7P8w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudefhedgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdvffejueetleefieeludduuefgteejleevfeekjeefieegheet ffdvkeefgedunecuffhomhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrd dvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CC9FB3064AB2; Wed, 18 Nov 2020 04:15:05 -0500 (EST) From: Thomas Monjalon To: Radha Mohan Cc: Jerin Jacob Kollanukkaran , Mahipal Challa , Radha Chintakuntla , Satha Koteswara Rao Kottidi , "dev@dpdk.org" , Veerasenareddy Burru , Satananda Burla , david.marchand@redhat.com Date: Wed, 18 Nov 2020 10:15:04 +0100 Message-ID: <4090240.s8fMJe6Fhk@thomas> In-Reply-To: References: <20201110001938.174839-1-radhac@marvell.com> <5264517.tcxCQdgLY6@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] maintainers: Update for OcteonTx2 DMA and EP X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 18/11/2020 05:15, Radha Mohan: > On Mon, Nov 16, 2020 at 12:28 PM Thomas Monjalon wrote: > > 16/11/2020 19:28, Radha Mohan: > > > On Fri, Nov 13, 2020 at 2:39 PM Thomas Monjalon wrote: > > > > 13/11/2020 20:18, Radha Mohan: > > > > > On Tue, Nov 10, 2020 at 11:57 PM Mahipal Challa wrote: > > > > > From: Radha Mohan > > > > > Sent: Tuesday, November 10, 2020 11:44 PM > > > > > > On Mon, Nov 9, 2020 at 4:20 PM Radha Mohan Chintakuntla wrote: > > > > > > > > > > > > > > Replace the maintainers for OcteonTx2 DMA and EP drivers. > > > > > > > > > > > > > > Signed-off-by: Radha Mohan Chintakuntla > > > > [...] > > > > > > >Adding previous maintainers to ack. > > > > > > Acked-by: Mahipal Challa > > > > > > > > > > > Thanks, > > > > > > Mahipal > > > > > > > > > > Hi Thomas, > > > > > Could you please pick this patch ? > > > > > > > > This low-priority patch has been sent 4 days ago, > > > > and was acked by only 1 maintainer 3 days ago. > > > > > > > > > > It was acked by both the old maintainers Satha Koteshwar and Mahipal > > > Challa. Maybe both of those emails didn't come on top of each other. > > > > I missed one. > > > > > > Why pushing? What is your fear exactly? > > > > > > Just want to make the transfer of ownership official in the mainline. > > > There's no fear I just normally wanted to send a reminder to you to > > > pick as it might be missed inclusion. If there's a guarantee that all > > > ack'ed patches will go automatically then I won't be sending any > > > reminder emails in future. > > > > It's OK to send reminder, but please wait at least a week. > > > > > > Why the new maintainers candidates have 0 and 2 contributions > > > > in git history? > > > > > > > These drivers requires some maintenance and likely expanded to support > > > future chips from Marvell. So you will not see contributions right > > > away. > > > So to become a maintainer one has to have prior contributions ? > > > > Yes: http://doc.dpdk.org/guides/contributing/patches.html#maintainers-and-sub-trees > > " > > Maintainers should have demonstrated a reasonable level of contributions or reviews to the component area. The maintainer should be confirmed by an ack from an established contributor. > > " > > How was this done without prior contributions? > http://git.dpdk.org/dpdk/commit/MAINTAINERS?id=238e3167ca869abf44fa50ead022d7fc3b99605b I asked a confirmation: http://inbox.dpdk.org/dev/1985242.AXpOyGb66D@thomas/ > The commit log says that he is a "new developer". So am I technically > to the community. > > Also the thing that puzzles me most is its a driver specific to > Marvell and both the previous maintainers are ok with the transfer but > a strange rule that probably applies to generic things of dpdk code > (which really makes sense there) comes as a blocker. Did I say it is a blocker? > And how does new driver go? For new drivers, the new maintainers arrive by contributing new code. > Lets say if either myself or veerasena have pushed a new driver now > who has to ack it for inclusion ? Isn't that like a chicken and egg > problem. Nobody has to ack for a new driver. > I am looking for clarifications as things are different in other open > source communities. > > > > Kind of makes odd sense as these drivers are specific to our chip and we > > > are changing ownership for maintaining them. > > > I do not understand why you have an issue here? > > > You don't like reminding then I understand. > > > > I don't like how you push new unconfirmed maintainers. > > Could you please explain above commit made into new maintainer? Listen: I say I don't like how pushy you are, that's all. In general it's very good to have new contributors. But please think how you can help instead of just requesting. We have a lot more important things to care at the moment to close the big release 20.11. If you want to help, you are welcome.