From patchwork Tue Jan 31 18:01:44 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Daniel Vetter X-Patchwork-Id: 9547937 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id E8563604DE for ; Tue, 31 Jan 2017 18:01:55 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id DAF3B2818E for ; Tue, 31 Jan 2017 18:01:55 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id CFCBF28249; Tue, 31 Jan 2017 18:01:55 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_MED, T_DKIM_INVALID autolearn=unavailable version=3.3.1 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 8C2582818E for ; Tue, 31 Jan 2017 18:01:55 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id C55D489BBD; Tue, 31 Jan 2017 18:01:53 +0000 (UTC) X-Original-To: dri-devel@lists.freedesktop.org Delivered-To: dri-devel@lists.freedesktop.org Received: from mail-wj0-x241.google.com (mail-wj0-x241.google.com [IPv6:2a00:1450:400c:c01::241]) by gabe.freedesktop.org (Postfix) with ESMTPS id 207A089BBD for ; Tue, 31 Jan 2017 18:01:52 +0000 (UTC) Received: by mail-wj0-x241.google.com with SMTP id le4so2248539wjb.0 for ; Tue, 31 Jan 2017 10:01:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id; bh=zEI4duiaHBfjtXfJp4Il8FlYkLAh0xNdshJiiFN2Z9Y=; b=NAytMQ8yzKjF/wG7LhPuVqP0VA86RIO7/WB7BIY6iIbD/qb/g/3WvqgUpKb1ZQ5HQa CMknOn8jXP0OHowabg0inQAZXz+1dI2fVXaqDLEYBIWAIzatqP5TWf+DPO3npWlcVvz6 cQ9N/9ERYMtandpG9pq33OEWwQJLVtoG+10Ys= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=zEI4duiaHBfjtXfJp4Il8FlYkLAh0xNdshJiiFN2Z9Y=; b=dX6CNk5WfAU+lZW7wDM0rfkrTPTSZQpfKyLZYIQoOXsplgok6XamjfpSo+tqwUH4Mf Rrx6FvT4JW62ZVTWTh52+7Kf5bqU9LKazc/9MIF3fa/2NiGbrUcFf0p5wuTBREr6llms gazNlugFYIs0mOdPTBJl0c6FTa+6lDljG2muRQ018E5ENlgFny/0ghefizJymUSVCnfZ +KHwyOWbvxIXm2opjLEQ2SrYhiIximGY27wKQh2kIWYu1ZoKvXIJnTtD1kqNe0hMrGMa hggpLITtTsDioSciiH6DpegkFlypyA97VLEfueCS8kveCDd3HQxpcbBwFjgMiDQmFG4a 9qNQ== X-Gm-Message-State: AIkVDXLcDwWXn1AxXJ6kYExWVBabo7cw5oszW8co/BEnPMpFC6CSHDZTJAJBQasZJFhUQQ== X-Received: by 10.28.227.84 with SMTP id a81mr1898605wmh.121.1485885710704; Tue, 31 Jan 2017 10:01:50 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:56c9:0:decc:6e78:7e96:b452]) by smtp.gmail.com with ESMTPSA id m29sm29559302wrm.38.2017.01.31.10.01.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 10:01:50 -0800 (PST) From: Daniel Vetter To: DRI Development Subject: [PATCH] drm-misc: Document small drivers expectations Date: Tue, 31 Jan 2017 19:01:44 +0100 Message-Id: <20170131180144.12780-1-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.11.0 Cc: Daniel Vetter , Intel Graphics Development , Gerd Hoffmann , Daniel Vetter , Shawn Guo X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" X-Virus-Scanned: ClamAV using ClamSMTP For the experiement we have right now Eric (with vc4) and Sean Paul (with rockchip and zte) volunteering, and Gerd (entire pile of qemu drivers) and Boris (atmel) are also considering to participate. I think that's enough to get started and figure things out as we go. I tried to summarize the main points from the rfc discussions into a short chapter. v2: Spelling fixes (Anholt). Cc: Boris Brezillon Cc: Eric Anholt Cc: Sean Paul Cc: Gerd Hoffmann Cc: Mark Yao Cc: Shawn Guo Acked-by: Sean Paul Acked-by: Gerd Hoffmann Acked-by: Boris Brezillon Acked-by: Eric Anholt Signed-off-by: Daniel Vetter --- drm-misc.rst | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/drm-misc.rst b/drm-misc.rst index 3d711ec60047..7f7233cf3c61 100644 --- a/drm-misc.rst +++ b/drm-misc.rst @@ -93,6 +93,36 @@ Right now the only hard merge criteria are: * See also the extensive `committer guidelines for drm-intel `_. +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: + +* 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 + enabling once a year), and if the series is really big (more than 20 patches) + it should probably be managed through a topic branch in drm-misc and with a + separate pull request to drm maintainer. dim_ supports this with the + create-branch command. + +* Group maintainership is assumed, i.e. all regular contributors (not just + the primary maintainer) will get commit rights. + +* Since even a broken driver is more useful than no driver minimal review + standards are a lot lower. The default should be some notes about what could + be improved in follow-up work and accepting patches by default. Maintainer + group for drivers can agree on stricter rules, especially when they have a + bigger user base that shouldn't suffer from regressions. + +* Minimal peer-review is also expected for drivers with just one contributor, + but obviously then only focuses on best practices for the interaction with drm + core and helpers. Plus a bit looking for common patterns in dealing with the + hardware, since display IP all has to handle the same issues in the end. In + most cases this will just along the lines of "Looks good, Ack". drm-misc + maintainers will help out with getting that review market going. + Tooling =======