I think the initial experiment worked fairly well, and the kickstarting of a review (well, ack/best practices really) market seems to work ok-ish too. I think we can try to make it (slowly) scale to more drivers, with driver teams interested in being part of drm-misc. I do think we need to be careful though, to make sure we don't overstretch the review/mentoring bandwidth and can improve process&tooling as we go.
Cc: Sumit Semwal <[email protected]> Cc: Gustavo Padovan <[email protected]> Cc: Jani Nikula <[email protected]> Cc: Sean Paul <[email protected]> Cc: Archit Taneja <[email protected]> Cc: Gerd Hoffmann <[email protected]> Cc: Boris Brezillon <[email protected]> Cc: Neil Armstrong <[email protected]> Cc: Mark Yao <[email protected]> Cc: Eric Anholt <[email protected]> Cc: Shawn Guo <[email protected]> Cc: Dave Airlie <[email protected]> Signed-off-by: Daniel Vetter <[email protected]> --- drm-misc.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drm-misc.rst b/drm-misc.rst index b6d01f2c7c2b..e4409cce8178 100644 --- a/drm-misc.rst +++ b/drm-misc.rst @@ -105,8 +105,8 @@ Small Drivers ============= Small drivers, where a full tree is overkill, can be maintained in drm-misc. For -now it's just an experiment with a few drivers to figure out a working process. -Slightly different rules apply: +now there's just a few drivers maintained in drm-misc, but we can slowly add +more to figure out how to make this scale. Slightly different rules apply: * Small is measured in patches merged per kernel release. The occasional big patch series is still acceptable if it's not a common thing (e.g. new hw -- 2.11.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
