From: Laura Abbott <firstname.lastname@example.org> To: John Stultz <email@example.com> Cc: lkml <firstname.lastname@example.org>, "Andrew F. Davis" <email@example.com>, Benjamin Gaignard <firstname.lastname@example.org>, Greg KH <email@example.com>, Sumit Semwal <firstname.lastname@example.org>, Liam Mark <email@example.com>, Brian Starkey <Brian.Starkey@arm.com>, Chenbo Feng <firstname.lastname@example.org>, Alistair Strachan <email@example.com>, dri-devel <firstname.lastname@example.org> Subject: Re: [RFC][PATCH 1/5 v2] dma-buf: Add dma-buf heaps framework Date: Fri, 15 Mar 2019 15:44:57 -0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CALAqxLXho_rwsdAY9u3=oTXukQnTzqfP_EFmwgdZm+A1bQRVuw@mail.gmail.com> On 3/15/19 2:29 PM, John Stultz wrote: > On Fri, Mar 15, 2019 at 1:18 PM Laura Abbott <firstname.lastname@example.org> wrote: >> >> On 3/5/19 12:54 PM, John Stultz wrote: >>> +DMA-BUF HEAPS FRAMEWORK >>> +M: Laura Abbott<email@example.com> >>> +R: Liam Mark<firstname.lastname@example.org> >>> +R: Brian Starkey<Brian.Starkey@arm.com> >>> +R: "Andrew F. Davis"<email@example.com> >>> +R: John Stultz<firstname.lastname@example.org> >>> +S: Maintained >>> +L: email@example.com >>> +L: firstname.lastname@example.org >>> +L: email@example.com (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! > > 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) > 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
next prev parent reply other threads:[~2019-03-15 22:44 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-05 20:54 [RFC][PATCH 0/5 v2] DMA-BUF Heaps (destaging ION) John Stultz 2019-03-05 20:54 ` [RFC][PATCH 1/5 v2] dma-buf: Add dma-buf heaps framework John Stultz 2019-03-06 16:12 ` Benjamin Gaignard 2019-03-06 16:57 ` John Stultz 2019-03-15 8:55 ` Christoph Hellwig 2019-03-06 16:27 ` Andrew F. Davis 2019-03-06 19:03 ` John Stultz 2019-03-06 21:45 ` Andrew F. Davis 2019-03-15 8:54 ` Christoph Hellwig 2019-03-15 20:24 ` Andrew F. Davis 2019-03-15 20:18 ` Laura Abbott 2019-03-15 20:49 ` Andrew F. Davis 2019-03-15 21:29 ` John Stultz 2019-03-15 22:44 ` Laura Abbott [this message] 2019-03-18 4:38 ` Sumit Semwal 2019-03-18 4:41 ` Sumit Semwal 2019-03-19 12:08 ` Brian Starkey 2019-03-19 15:24 ` Andrew F. Davis 2019-03-21 21:16 ` John Stultz 2019-03-27 14:53 ` Greg KH 2019-03-28 6:09 ` John Stultz 2019-03-05 20:54 ` [RFC][PATCH 2/5 v2] dma-buf: heaps: Add heap helpers John Stultz 2019-03-13 20:18 ` Liam Mark 2019-03-13 21:48 ` Andrew F. Davis 2019-03-13 22:57 ` Liam Mark 2019-03-13 23:42 ` Andrew F. Davis 2019-03-15 9:06 ` Christoph Hellwig 2019-03-19 15:03 ` Andrew F. Davis 2019-03-21 20:01 ` John Stultz 2019-03-19 14:26 ` Brian Starkey 2019-03-21 20:11 ` John Stultz 2019-03-21 20:35 ` Andrew F. Davis 2019-03-21 20:43 ` Andrew F. Davis 2019-03-05 20:54 ` [RFC][PATCH 3/5 v2] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz 2019-03-06 16:01 ` Benjamin Gaignard 2019-03-11 5:48 ` John Stultz 2019-03-13 20:20 ` Liam Mark 2019-03-13 22:49 ` John Stultz 2019-03-15 9:06 ` Christoph Hellwig 2019-03-05 20:54 ` [RFC][PATCH 4/5 v2] dma-buf: heaps: Add CMA heap to dmabuf heapss John Stultz 2019-03-06 16:05 ` Benjamin Gaignard 2019-03-21 20:15 ` John Stultz 2019-03-15 9:06 ` Christoph Hellwig 2019-03-15 20:08 ` John Stultz 2019-03-19 14:53 ` Brian Starkey 2019-03-05 20:54 ` [RFC][PATCH 5/5 v2] kselftests: Add dma-heap test John Stultz 2019-03-06 16:14 ` Benjamin Gaignard 2019-03-06 16:35 ` Andrew F. Davis 2019-03-06 18:19 ` John Stultz 2019-03-06 18:32 ` Andrew F. Davis 2019-03-06 17:01 ` John Stultz 2019-03-15 20:07 ` Laura Abbott 2019-03-15 20:13 ` John Stultz 2019-03-15 20:49 ` Laura Abbott 2019-03-13 20:23 ` Liam Mark 2019-03-13 20:11 ` [RFC][PATCH 0/5 v2] DMA-BUF Heaps (destaging ION) Liam Mark 2019-03-13 22:30 ` John Stultz 2019-03-13 23:29 ` Liam Mark 2019-03-19 16:54 ` Benjamin Gaignard 2019-03-19 16:59 ` Andrew F. Davis 2019-03-19 21:58 ` Rob Clark 2019-03-19 22:36 ` John Stultz 2019-03-20 9:16 ` Benjamin Gaignard 2019-03-20 14:44 ` Andrew F. Davis 2019-03-20 15:59 ` Benjamin Gaignard 2019-03-20 16:11 ` John Stultz 2019-03-15 20:34 ` Laura Abbott 2019-03-15 23:15 ` Jerome Glisse 2019-03-16 0:16 ` John Stultz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --cc=Brian.Starkey@arm.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC][PATCH 1/5 v2] dma-buf: Add dma-buf heaps framework' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).