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 A6195A04E6; Wed, 18 Nov 2020 05:16:06 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 32CC258C4; Wed, 18 Nov 2020 05:16:04 +0100 (CET) Received: from mail-lf1-f68.google.com (mail-lf1-f68.google.com [209.85.167.68]) by dpdk.org (Postfix) with ESMTP id 75BA34C90 for ; Wed, 18 Nov 2020 05:16:01 +0100 (CET) Received: by mail-lf1-f68.google.com with SMTP id u19so995951lfr.7 for ; Tue, 17 Nov 2020 20:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xhFRIXd1EEM1nSmNx6HG8bpsAoGW+ISNE2nvMgwjabc=; b=Ft2trHgllevUAtpP6xQfJSYfShEXN9n09FRAfion4A8ARRhX3HP7FIAUdl03g/5Lue VJiUuywca2vXIbWYrSdm1O4Ayz0472RkRaDc2NBXO+ao5rm9H0TAJr3yuP/W8UHBxuDN SbsIpnsW0TMxoyCr1dzSDqybeTyjZ5Vnq/zhfa71x0A3SnrbzuGQsfuoeERIq82eqzdz cP5D+e4qsOmMUxyH5q/ef1wuZLdBohD0Az0XzWh8Dso7uyzplSpFBSMjk+/sW4mRRljw 7k9ArKPZ4AITpb8yyuwrW6i/mYEMiEIO0JV61/xA1dqpGGcDZQdVF0G6IyqggAOhaxP/ E87g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xhFRIXd1EEM1nSmNx6HG8bpsAoGW+ISNE2nvMgwjabc=; b=fAzbFolY0N7zUWB6WUJ63teH4MseT2eEQ9W5+8kGP9vjYoFPbAeQj2KBrlGmAP8sqH sTjtnmyR9K9hlUQ4IZ0KVpyhuoXACCxQ48NM9DvQtGtejuh7wz1wtMvleGNdyhO33zzj +yBX932mT0FlXBOnutjRrQyW7Efxumi/LlkiOj1i6jSTVqPpSFpgUKknAVlcKgNpAmW0 ZR70VsNu2fx11+tU1LGmdUpelqSC3tWALU5H+2HZpQGVKWI6p9jEilDtD2LtjWL5eXJU OvWqSEmlgo3rRX1TPDm3Wdb9/BVoAcbjKcas5Ygt7WYEE5gepHNOsPNg9S7y0iGaEhU6 cEdg== X-Gm-Message-State: AOAM532u+Cq1UMlvYo4Rf1+rmkzfWEbNd4Q8QZzldCIlCp/U38HpOnZd L3q/JJqKOC7Y6lQI3YjTtPo9R3DZ500fPoUNUrw= X-Google-Smtp-Source: ABdhPJzfyAJKWdUG7XWQ/+fzQZHiYI5Jn+lg7HR1VEth6QcjBKIxOMO/MULBlPe3DECbs2hcgCOPHzIV+bxT1nr5+RI= X-Received: by 2002:ac2:51db:: with SMTP id u27mr2927478lfm.32.1605672960006; Tue, 17 Nov 2020 20:16:00 -0800 (PST) MIME-Version: 1.0 References: <20201110001938.174839-1-radhac@marvell.com> <17179405.ZpaCnA1xSU@thomas> <5264517.tcxCQdgLY6@thomas> In-Reply-To: <5264517.tcxCQdgLY6@thomas> From: Radha Mohan Date: Tue, 17 Nov 2020 20:15:48 -0800 Message-ID: To: Thomas Monjalon Cc: Jerin Jacob Kollanukkaran , Mahipal Challa , Radha Chintakuntla , Satha Koteswara Rao Kottidi , "dev@dpdk.org" , Veerasenareddy Burru , Satananda Burla Content-Type: text/plain; charset="UTF-8" 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" 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 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. And how does new driver go? 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. 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? > >