lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 28 Nov 2017 15:42:36 -0800
From:   Doug Anderson <dianders@...omium.org>
To:     Sandy Huang <hjc@...k-chips.com>
Cc:     Heiko Stuebner <heiko@...ech.de>, dri-devel@...ts.freedesktop.org,
        David Airlie <airlied@...ux.ie>,
        "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Sean Paul <seanpaul@...omium.org>, daniel@...ll.ch
Subject: Re: [PATCH] MAINTAINERS: change maintainer for Rockchip drm drivers

Hi,

On Sun, Nov 26, 2017 at 6:22 PM, Sandy Huang <hjc@...k-chips.com> wrote:
> Hi Daniel,
>     I register the account and get the drm-misc commit rights now, thanks.
>
>
> 在 2017/11/24 22:51, Daniel Vetter 写道:
>>
>> 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@...k-chips.com>
>>>>> Cc: Heiko Stuebner <heiko@...ech.de>
>>>>>
>>>>> Signed-off-by: Mark Yao <mark.yao@...k-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

I just got a bounced mail from Mark Yao's old email address and
noticed that linux-next still shows him as the maintainer.  It'd be
great if we could land the change to update the MAINTAINERS file.  :-P

-Doug

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ