[PATCH] MAINTAINERS: change maintainer for Rockchip drm drivers
daniel at ffwll.ch
Fri Nov 24 06:51:06 PST 2017
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 at rock-chips.com>
> > > Cc: Heiko Stuebner <heiko at sntech.de>
> > >
> > > Signed-off-by: Mark Yao <mark.yao at 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:
Software Engineer, Intel Corporation
More information about the Linux-rockchip