From: Daniel Vetter <daniel@ffwll.ch>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>
Subject: Re: [PATCH v1 1/1] drm: drop drm_bus from todo
Date: Tue, 29 Jan 2019 18:00:19 +0100 [thread overview]
Message-ID: <20190129170019.GW3271@phenom.ffwll.local> (raw)
In-Reply-To: <20190129141800.GA10955@ravnborg.org>
On Tue, Jan 29, 2019 at 03:18:00PM +0100, Sam Ravnborg wrote:
> Hi Daniel.
>
> >
> > Sam, want drm-misc commit rights to start merging your own stuff? Assuming
> > you plan to stick around ofc ... I'll also ask the drm-misc maintainers
> > whether that's ok.
>
> The plan is to re-submit the Atmel LCDC DRM driver when I find enough time
> to finish it. All coding is done and it builds, I 'only' need to make it work.
>
> When I submit the driver the plan is to share the maintainer role for
> both Atmel based DRM drivers (hlcdc + lcdc).
> So it would make sense to gain drm-misc commit rights at least then.
>
> Last time I looked at it I was stucked in the keys required and the tools
> I needed to learn. This was not really where I had energy to spend the effort.
Can I motivate you some more? I'm happy to ramp up people for a bit, but I
can't do patch review&applying for everyone. Wouldn't scale. Expect me to
become increasingly annoying about this :-)
-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
next prev parent reply other threads:[~2019-01-29 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 19:27 [PATCH v1 1/1] drm: drop drm_bus from todo Sam Ravnborg
2019-01-27 11:00 ` David Herrmann
2019-01-29 8:54 ` Daniel Vetter
2019-01-29 14:18 ` Sam Ravnborg
2019-01-29 17:00 ` Daniel Vetter [this message]
2019-01-29 15:29 ` Sean Paul
2019-04-27 16:22 ` Sam Ravnborg
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=20190129170019.GW3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox