From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] [RFC] MAINTAINERS: Daniel for drm co-maintainer
Date: Wed, 12 Dec 2018 14:37:10 +0100 [thread overview]
Message-ID: <20181212143710.4ebacd18@bbrezillon> (raw)
In-Reply-To: <20181210103001.30549-1-daniel.vetter@ffwll.ch>
On Mon, 10 Dec 2018 11:30:01 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> lkml and Linus gained a CoC, and it's serious this time. Which means
> my no 1 reason for declining to officially step up as drm maintainer
> is gone, and I didn't find any new good excuse.
>
> I chatted with a few people in private already, and the biggest
> concern is that I mislay my community hat and start running around
> with my intel hat only. Or some other convenient abuse of trust.
>
> That's why this patch doesn't just need a lot of acks that mean "yeah
> seems fine to me", but a lot of acks that mean "yeah we'll tell you
> when you're over the line and usurp you from that comfy chair if you
> don't get it". Which I think we've been done a fairly good job here at
> dri-devel in general, but better to be clear.
>
> Rough idea is that I'll do this for maybe 2-3 years, helping Dave
> figure out a group model for drm overall. And getting the tooling and
> infrastructure for that off the ground. Then step down again because
> some other shiny thing that needs chasing. Of course as plans tend to
> do, this one will probably pan out a bit different in reality.
>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Acked-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7e05aa20b0ab..2c4cd038df2a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4849,6 +4849,7 @@ F: include/uapi/drm/vmwgfx_drm.h
>
> DRM DRIVERS
> M: David Airlie <airlied@linux.ie>
> +M: Daniel Vetter <daniel@ffwll.ch>
> L: dri-devel@lists.freedesktop.org
> T: git git://anongit.freedesktop.org/drm/drm
> B: https://bugs.freedesktop.org/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-12 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 10:30 [PATCH] [RFC] MAINTAINERS: Daniel for drm co-maintainer Daniel Vetter
2018-12-10 10:39 ` Christian König
2018-12-10 16:35 ` Rodrigo Vivi
2018-12-10 19:43 ` Alex Deucher
2018-12-10 23:42 ` Eric Anholt
2018-12-12 1:26 ` Daniel Stone
2018-12-11 8:09 ` Gerd Hoffmann
2018-12-11 11:17 ` Liviu Dudau
2018-12-12 10:12 ` Daniel Vetter
2018-12-13 11:09 ` Liviu Dudau
2018-12-12 11:57 ` Neil Armstrong
2018-12-12 13:25 ` Thierry Reding
2018-12-12 13:37 ` Boris Brezillon [this message]
2018-12-12 14:17 ` Thomas Hellstrom
2018-12-12 15:45 ` Sean Paul
2018-12-12 23:44 ` Dave Airlie
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=20181212143710.4ebacd18@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=torvalds@linux-foundation.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.