From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Sean Paul <seanpaul@chromium.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: RFC: drm-misc for small drivers?
Date: Fri, 27 Jan 2017 07:32:42 +0100 [thread overview]
Message-ID: <CAKMK7uHLb8w6tjRVchTQ6fvayw8Fx5fNFrSAeo99P5HYbLChUw@mail.gmail.com> (raw)
In-Reply-To: <20170126191121.GA10104@art_vandelay>
On Thu, Jan 26, 2017 at 8:11 PM, Sean Paul <seanpaul@chromium.org> wrote:
> On Thu, Jan 26, 2017 at 06:08:42PM +0100, Daniel Vetter wrote:
>> - Should it be an entire separate tree for soc drivers? Problem here
>> is that we lack a volunteer group (and imo it really should be a group
>> to avoid the single-maintainer troubles) to run that.
>
> Big +1. In addition to spreading out the workload, driver maintainers should
> still exercise ownership/stewardship.
Big +1 on separate driver tree, or that we'll probably can't get it
because no volunteers? For spreading out the workload, I don't expect
(or want) that this will cause more work for the existing drm-misc
group. Well, a few minutes more for the pull request summaries maybe,
but definitely no expectation that suddenly all of drm-misc helps out
with reviewing driver patches. That won't work.
>> - Who's elligible? I think we could start small with a few volunteers
>> and their drivers, and then anyone who's willing.
>
> I think we could safely volunteer some drivers we haven't seen pull requests
> from in a while.
Hm, I didn't think about drivers which aren't well-maintained. But if
there's a volunteer group we can do that ofc, but maybe not start out
with forcing it ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-27 6:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 17:08 RFC: drm-misc for small drivers? Daniel Vetter
2017-01-26 17:42 ` Liviu Dudau
2017-01-26 19:12 ` Sean Paul
2017-01-26 20:48 ` Liviu Dudau
2017-01-27 6:55 ` Daniel Vetter
2017-01-27 9:44 ` Liviu Dudau
2017-01-26 19:57 ` Daniel Vetter
2017-01-26 20:54 ` Liviu Dudau
2017-01-30 9:30 ` Gerd Hoffmann
2017-01-30 9:49 ` Daniel Vetter
2017-01-30 9:53 ` Tomi Sarvela
2017-01-26 19:11 ` Sean Paul
2017-01-27 6:32 ` Daniel Vetter [this message]
2017-01-27 16:30 ` Sean Paul
2017-01-26 19:48 ` Eric Anholt
2017-01-27 6:52 ` Daniel Vetter
2017-01-27 16:50 ` Alex Deucher
2017-01-30 8:24 ` Daniel Vetter
2017-01-30 10:15 ` Boris Brezillon
2017-01-31 7:48 ` Daniel Vetter
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 \
--in-reply-to=CAKMK7uHLb8w6tjRVchTQ6fvayw8Fx5fNFrSAeo99P5HYbLChUw@mail.gmail.com \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.