From: Daniel Vetter <daniel@ffwll.ch>
To: Heiko Stuebner <heiko@sntech.de>
Cc: dri-devel@lists.freedesktop.org, Sandy Huang <hjc@rock-chips.com>,
Daniel Vetter <daniel@ffwll.ch>,
Mark Yao <mark.yao@rock-chips.com>,
David Airlie <airlied@linux.ie>,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: change maintainer for Rockchip drm drivers
Date: Fri, 24 Nov 2017 15:51:06 +0100 [thread overview]
Message-ID: <20171124145106.hdtybw3hgizlg6gs@phenom.ffwll.local> (raw)
In-Reply-To: <83984459.7UdiCfbSkg@phil>
On Fri, Nov 24, 2017 at 09:28:59AM +0100, Heiko Stuebner wrote:
> Hi Daniel,
>
> [somehow my email address seems to have gotten lost, so
> only saw this by chance on the list itself now.
> I've also re-added Sandy to the recipients]
>
> Am Montag, 20. November 2017, 08:48:48 CET schrieb Daniel Vetter:
> > On Mon, Nov 13, 2017 at 06:15:31PM +0800, Mark Yao wrote:
> > > For personal reasons, Mark Yao will leave rockchip,
> > > can not continue maintain drm/rockchip, Sandy Huang
> > > will take over the drm/rockchip.
> > >
> > > Cc: Sandy Huang <hjc@rock-chips.com>
> > > Cc: Heiko Stuebner <heiko@sntech.de>
> > >
> > > Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> >
> > Since rockchip is in drm-misc that means we need a new maintainer who also
> > has drm-misc commit rights. Sandy doesn't yet, so if Sandy is going to be
> > the new maintainer we need to fix that.
> >
> > Also, Heiko, are you interested in becoming co-maintainer? With commit
> > rights and all.
>
> I always feel somewhat inadequate judging the fast-paced drm stuff, as in
> the past once I got my head wrapped around something, drm always
> somehow moved another mile already ;-) .
>
> But somewhere I read that drm-pace for big changes is supposed to slow a
> bit now that atomic modesetting is done in a lot of places, so we could give
> co-maintainership for the Rockchip-drm a try - with Sandy wearing the
> actual hat for big changes though ;-) .
Yeah I think on the modeset side it calmed down a lot. We're still
fine-tuning the helper libraries as we're figuring out better ways to
write drivers. But right now I think a lot of the action is all in details
not relevant for many drivers.
If Sandy's ok with that too pls request an fd.o account for drm-misc and
set up the tooling per our quickstart guide:
https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html#quickstart
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2017-11-24 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 10:15 [PATCH] MAINTAINERS: change maintainer for Rockchip drm drivers Mark Yao
2017-11-20 7:48 ` Daniel Vetter
2017-11-24 8:28 ` Heiko Stuebner
2017-11-24 14:51 ` Daniel Vetter [this message]
2017-11-27 2:22 ` Sandy Huang
2017-11-28 23:42 ` Doug Anderson
2017-11-29 9:54 ` Daniel Vetter
2017-11-29 9:55 ` Heiko Stübner
2017-11-29 14:24 ` [PATCH v2] " Sean Paul
2017-11-29 14:27 ` Sean Paul
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=20171124145106.hdtybw3hgizlg6gs@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.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).