RFC: drm-misc for small drivers?

[Daniel Vetter]

On Thu, Jan 26, 2017 at 9:48 PM, Liviu Dudau <liviu at dudau.co.uk> wrote:
>> I'm not certain number of people is a good metric, TBH. There are cases
>> where a lot of people are working on a driver, but the patches are not being
>> merged to the maintainer tree. In these cases, it makes sense to migrate the
>> driver to -misc and have the community merge the patches.
>
> Sorry, I should've been more explicit: I was referring to the number of
> contributors with public commit rights, not all the engineers involved. In
> Mali DP's case we do most of the development in the open, so all the engineers
> are free to merge the patches into the current public git tree after internal
> review that tries to catch the evident issues.

Not sure, but this sounds like you do internal review and then just
push to the public tree. That's not good, since it makes cross-driver
collab harder, and it makes it much harder for external people to
contribute to your driver in general. Upstream is about cross
vendor/user/osv/whomever collaboration in the open, if you really do
review internall I strongly urge you to do all patch submission&review
on dri-devel. That's how all the other drivers work (well
amd/i915/nouveau have their own separate mailing lists because we'd
drown dri-devel), and it's the expectation. It would definitely be the
expectation if arm display is managed in drm-misc :-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch