Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp97453img; Sun, 17 Mar 2019 21:42:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqxLl1/IXEE/Fh6DnyNpt+OI+waw8RsLQG5Q00B8WOL19WRH8LpTnj1foLnGyvlpdpGiBWn5 X-Received: by 2002:a63:4e57:: with SMTP id o23mr14987883pgl.368.1552884144220; Sun, 17 Mar 2019 21:42:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552884144; cv=none; d=google.com; s=arc-20160816; b=zPxFH1G+SV9nUtQQopmA22hk5mfSsxQRS8HhzRaFaf3K8yNzvlil117bZd2lip7S2e PqeqawOv91mYX0ZsmW3i14Cvcd4HWxkBri/OdPhYZZhQjcWPsabOI+a2d/zsgwkPiuye 0JXvvSswBBlJR8Q3kc1L4biS2Ks0aSSz/GoEhbqovWyKVWCCr1Oo0gLUyhr/xYNSG1vr BSRNLaHoz8JHsq+VXLRvzb0D0r2tGqATLWh8n9NlNgDTvXUMuIpQ0S9js3S+HdcCo1p6 NOJ1nxIMn1/VbVcCgtk8LxTnyB+FLE0oc9pK+YOQkn2LaWmtR1kSt2jb3q+lsre4/wAi ZmKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=ltBVV44SsuqJ8Mxo4h0OwbaYZ4cq62RESnfO6q7Ji90=; b=Rzllo3BIlG6F+m7WCEDHtmn1N0Z1iNBYXLw1QDqkf00tpQ1JDuhPEYyJlBRydh/JcT Oomr3V5ohYiBpqVMCKVMtwJfd8ogErFz6NO0kpwUz1sPAzL5Bt1X50n6hmzads12Lhzh Qg9/7EB957hDQm29r05cZWSCb3eo1CVrxBJrVKBWz6r8cmSglgisMuoaz8qkkKtzoYp6 kU07bLvXXEXnLzBiD5LWytDr7M75cK9D3Y+uRWZel3cBLrBJPg9CUlRj6sZOp88Nb/yo x6Jptc+7lN/OP3rGgCDjk2de3OhitCx1H94U4hml6B21UJIYtTCXWqqHzajAckBmb+3x 2cJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Sd9+XkNo; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r7si4437556pfn.144.2019.03.17.21.42.07; Sun, 17 Mar 2019 21:42:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Sd9+XkNo; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727012AbfCRElb (ORCPT + 99 others); Mon, 18 Mar 2019 00:41:31 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:33175 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725896AbfCRElb (ORCPT ); Mon, 18 Mar 2019 00:41:31 -0400 Received: by mail-ot1-f67.google.com with SMTP id q24so13309350otk.0 for ; Sun, 17 Mar 2019 21:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ltBVV44SsuqJ8Mxo4h0OwbaYZ4cq62RESnfO6q7Ji90=; b=Sd9+XkNo4Lt54ydKJHdvq84AIUJX9PQQMRaB2L0aafChhepf1CesU613CtWVhPggqa ULJcqejZST1dtGolaI3EUg6ECle17fjviWp7Gj8pInqdP2axsBRyqMMUS3xZYoTHaF76 H4R8K44PMnailBOhl8FRe52GmClJ8CX3shOfTpW/KUvdTKFd87wygZvC9y8/GJcFTDIE +39GatzZSjjwJ2Wc6MAatBUD1/Oca8Xq5bhBDj/Y7dLOtJjIZ/YK27auMk2Y7ZA1n9Zx I6Nn+Sp/DZVvqQkPnoRnjkLgPToOF7u1w6kaq5bMjNPPmtpDq/ziQRVy5ipX/mehTx1R tiLQ== 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=ltBVV44SsuqJ8Mxo4h0OwbaYZ4cq62RESnfO6q7Ji90=; b=f4OV502kAHLQuhouUZNLhl0MkdHLRBcDd6eh1kbvdmIakpZcIZbk9CVLnAiO5Er/Cw 21E5gSnNzpsjsU920mwOcPf167nyEwVMpCmZdAYbSQjIlihkmRCF+oTglVQo7s8xF898 5I5vasP/hlDHhDsZ4muOyKixodV+9W9mBeoNYGWFE/5aEXSTnkVQAXIy8ZvE386YlxGw c96IbhsaE4aTNyEoaU6VEiYpHg6ycYb0I4fwJGgWLZW9uWO9ctGFIascEDbtQLkX8k8t H1WdzwMcruwRFccc1eMsMXBC/vsboKfmtP8nFtrpSxp2jp1dzMZyyCHItyWpXiI+z72N dLhA== X-Gm-Message-State: APjAAAXEHS4Q+/mAT27QE5t00RSOKA3Dlk/1V33HF2as0OL3xSjhsfyq ww6zWiPg65zJbg0bQq1eru0YgfR/ib+dVftAzG3czw== X-Received: by 2002:a9d:6c0b:: with SMTP id f11mr9996294otq.293.1552884090213; Sun, 17 Mar 2019 21:41:30 -0700 (PDT) MIME-Version: 1.0 References: <1551819273-640-1-git-send-email-john.stultz@linaro.org> <1551819273-640-2-git-send-email-john.stultz@linaro.org> <86b9ef2e-99f7-ad8c-dbfc-418c1538a0a8@redhat.com> In-Reply-To: <86b9ef2e-99f7-ad8c-dbfc-418c1538a0a8@redhat.com> From: Sumit Semwal Date: Mon, 18 Mar 2019 10:11:18 +0530 Message-ID: Subject: Re: [RFC][PATCH 1/5 v2] dma-buf: Add dma-buf heaps framework To: Laura Abbott Cc: John Stultz , lkml , "Andrew F. Davis" , Benjamin Gaignard , Greg KH , Liam Mark , Brian Starkey , Chenbo Feng , Alistair Strachan , dri-devel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 16 Mar 2019 at 04:15, Laura Abbott wrote: > > On 3/15/19 2:29 PM, John Stultz wrote: > > On Fri, Mar 15, 2019 at 1:18 PM Laura Abbott wrote: > >> > >> On 3/5/19 12:54 PM, John Stultz wrote: > >>> +DMA-BUF HEAPS FRAMEWORK > >>> +M: Laura Abbott > >>> +R: Liam Mark > >>> +R: Brian Starkey > >>> +R: "Andrew F. Davis" > >>> +R: John Stultz > >>> +S: Maintained > >>> +L: linux-media@vger.kernel.org > >>> +L: dri-devel@lists.freedesktop.org > >>> +L: linaro-mm-sig@lists.linaro.org (moderated for non-subscribers) > >>> +F: include/uapi/linux/dma-heap.h > >>> +F: include/linux/dma-heap.h > >>> +F: drivers/dma-buf/dma-heap.c > >>> +F: drivers/dma-buf/heaps/* > >>> +T: git git://anongit.freedesktop.org/drm/drm-misc > >> > >> So I talked about this with Sumit privately but I think > >> it might make sense to have me step down as maintainer when > >> this goes out of staging. I mostly worked on Ion at my > >> previous position and anything I do now is mostly a side > >> project. I still want to see it succeed which is why I > >> took on the maintainer role but I don't want to become blocking > >> for people who have a stronger vision about where this needs > >> to go (see also, I'm not working with this on a daily basis). > >> > >> If you just want someone to help review or take patches > >> to be pulled, I'm happy to do so but I'd hate to become > >> the bottleneck on getting things done for people who > >> are attempting to do real work. > > > > I worry this will make everyone to touch the side of their nose and > > yell "NOT IT!" :) > > > > First of all, thank you so much for your efforts maintaining ION along > > with your attempts to drag out requirements from interested parties > > and the numerous attempts to get collaborative discussion going at > > countless conferences! Your persistence and continual nudging in the > > face of apathetic private users of the code probably cannot be > > appreciated enough! I totally second John here - the persistence has been inspiring to me personally as well :) > > > > Your past practical experience with ION and active work with the > > upstream community made you a stand out pick for this, but I > > understand not wanting to be eternally stuck with a maintainership if > > your not active in the area. I'm happy to volunteer as a neutral > > party, but I worry my limited experience with some of the more > > complicated usage would make my opinions less informed then they > > probably need to be. Further, as a neutral party, Sumit would > > probably be a better pick since he's already maintaining the dmabuf > > core. > > > > Honestly if you're doing the work to re-write everything, I > think you're more than qualified to be the maintainer. I > would also support Sumit as well. > > > So I'd nominate Andrew, Liam or Benjamin (or all three?) as they all > > have more practical experience enabling past ION heaps on real devices > > and have demonstrated active interest in working in the community. > > > > I do think this would benefit both from multiple maintainers and > from maintainers who are actively using the framework. Like I > said, I can still be a maintainer but I think having some comaintainers > would be very helpful (and I'd support any of the names you've > suggested) If it's required, I am happy to co-maintain - we could even follow the drm-misc model of multiple co-maintainers. I will support any or all of the names above as well :) > > > So, in other words... NOT IT! :) > > I think you have to shout "Noes goes" first. :) > > > -john > > > > Thanks, > Laura > > P.S. For the benefit of anyone who's confused, > https://en.wikipedia.org/wiki/Nose_goes Best, Sumit.