All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Daniel Vetter <daniel@ffwll.ch>
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 15:18:00 +0100	[thread overview]
Message-ID: <20190129141800.GA10955@ravnborg.org> (raw)
In-Reply-To: <20190129085437.GL3271@phenom.ffwll.local>

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.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-01-29 14:18 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 [this message]
2019-01-29 17:00       ` Daniel Vetter
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=20190129141800.GA10955@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.com \
    --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 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.