From: Lucas Stach <l.stach@pengutronix.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Dave Airlie <airlied@linux.ie>,
Philippe Cornu <philippe.cornu@st.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: More drm-panel help volunteers?
Date: Fri, 13 Jul 2018 10:09:19 +0200 [thread overview]
Message-ID: <1531469359.3163.75.camel@pengutronix.de> (raw)
In-Reply-To: <CAKMK7uF-WKX6vEqJd7qK5S38kWj=juv88HEiqX7KT-Z26+rcLw@mail.gmail.com>
Hi Daniel,
Am Mittwoch, den 11.07.2018, 20:07 +0200 schrieb Daniel Vetter:
> Hi all,
>
> I chatted a bit with Thierry about drm-panel, and state of things
> still seems to be that when Thierry's on vacations/leave/busy patches
> don't move. So I looked at people with a few patches who could be
> volunteered to sometimes help out with review&merging:
>
> 31 Thierry Reding
> 16 Philipp Zabel
> 11 Lucas Stach
> 9 Ajay Kumar
> 9 Alexandre Courbot
> 8 Philippe CORNU
> 6 Boris Brezillon
> 6 Maxime Ripard
> 6 Stefan Agner
> 5 Arnd Bergmann
> 5 Dave Airlie
> 5 Yakir Yang
>
> There's fairly little patch activity going on in drm/panel, main goal
> would be just to reduce the occasional long waits (recently a
> contributor pinged 3 times or so every few weeks for feedback).
>
> Philipp Z and Lucas, either of you interested in drm-misc commit
> rights and occasionally scanning for drm-panel patches?
Philipp is on vacation right now, so don't expect an quick answer.
I for one already have commit rights to drm-misc (though I haven't used
them yet, as the initial setup overhead has kept me from trying), so if
Thierry needs a hand I could certainly help out a bit.
I don't feel fully qualified to look at the more complex panel stuff,
but at least making sure that simple panel patches don't get stuck
should be okay.
Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-13 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 18:07 More drm-panel help volunteers? Daniel Vetter
2018-07-13 7:28 ` Daniel Vetter
2018-07-13 8:09 ` Lucas Stach [this message]
2018-07-13 8:38 ` Daniel Vetter
2018-07-17 14:14 ` Philipp Zabel
2018-08-06 8:20 ` Daniel Vetter
2018-08-14 9:15 ` Philipp Zabel
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=1531469359.3163.75.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=airlied@linux.ie \
--cc=boris.brezillon@bootlin.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=philippe.cornu@st.com \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).