Thierry Reding <thierry.reding@xxxxxxxxx> writes: > [ Unknown signature status ] > On Tue, Jan 31, 2017 at 09:38:53AM -0500, Sean Paul wrote: >> On Tue, Jan 31, 2017 at 09:54:49AM +0100, Thierry Reding wrote: >> > On Tue, Jan 31, 2017 at 09:01:07AM +0900, Inki Dae wrote: >> > > >> > > >> > > 2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글: >> > > > Dear Thierry, >> > > > >> > > > Could you please review this patch? >> > > >> > > Thierry, I think this patch has been reviewed enough but no comment >> > > from you. Seems you are busy. I will pick up this. >> > >> > Sorry, but that's not how it works. This patch has gone through 8 >> > revisions within 4 weeks, and I tend to ignore patches like that until >> > the dust settles. >> > >> >> Seems like the dust was pretty settled. It was posted on 1/11, pinged on 1/24, >> and picked up on 1/31. I don't think it's unreasonable to take it through >> another tree after that. >> >> I wonder if drm_panel would benefit from the -misc group maintainership model >> as drm_bridge does. By spreading out the workload, the high-maintenance >> patches would hopefully find someone to shepherd them through. > > Except that nobody except me really cares. If we let people take patches > through separate trees or group-maintained trees they'll likely go in > without too much thought. DRM panel is somewhat different from core DRM > in this regard because its infrastructure is minimal and there's little > outside the panel-simple driver. So we're still at a stage where we need > to fine-tune what drivers should look like and how we can improve. I would love to care and participate in review, but with the structure of your tree you're the only one whose review counts, so I don't participate. As is, I'm stuck out here with my panel driver I submitted on December 14th completely ignored, and no other developer will look at it because their review doesn't count and only yours does. I would love for drm-panel to be moved under -misc.
Attachment:
signature.asc
Description: PGP signature
