From: Daniel Vetter <daniel@ffwll.ch>
To: Lukas Wunner <lukas@wunner.de>
Cc: Ben Widawsky <ben@bwidawsk.net>,
dim-tools@lists.freedesktop.org,
Petri Latvala <petri.latvala@intel.com>,
Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Keith Packard <keithp@keithp.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Kenneth Graunke <kenneth@whitecape.org>,
"Kristian H . Kristensen" <hoegsberg@google.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Subject: Re: [PATCH] drm-misc.rst: Document commit rights
Date: Mon, 30 Apr 2018 14:53:57 +0200 [thread overview]
Message-ID: <20180430125357.GI12521@phenom.ffwll.local> (raw)
In-Reply-To: <20180426145423.GA30009@wunner.de>
On Thu, Apr 26, 2018 at 04:54:23PM +0200, Lukas Wunner wrote:
> On Thu, Apr 26, 2018 at 04:25:57PM +0200, Daniel Vetter wrote:
> > This is the exact same text as proposed&merged for igt:
> >
> > https://patchwork.kernel.org/patch/10339739/
> >
> > With one minor change: Both regular contributions to the kernel
> > overall and to userspace graphics counts. We've gained a few
> > committers in the past who are coming from arm-soc platform work and
> > similar areas, to upstream&maintain drm drivers for their platform.
>
> FWIW,
> Acked-by: Lukas Wunner <lukas@wunner.de>
Pushed with Dave's irc-ack.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-30 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 14:25 [PATCH] drm-misc.rst: Document commit rights Daniel Vetter
2018-04-26 14:29 ` Daniel Vetter
2018-04-26 14:54 ` Lukas Wunner
2018-04-30 12:53 ` Daniel Vetter [this message]
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=20180430125357.GI12521@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexander.deucher@amd.com \
--cc=arkadiusz.hiler@intel.com \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@google.com \
--cc=jani.nikula@intel.com \
--cc=keithp@keithp.com \
--cc=kenneth@whitecape.org \
--cc=lukas@wunner.de \
--cc=petri.latvala@intel.com \
--cc=rodrigo.vivi@intel.com \
/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.