linux-kernel - Re: [RESEND][PATCH v3 00/26] drm: Kirin driver cleanups to prep for Kirin960 support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190819044054.GA8554@ravnborg.org>
Date:   Mon, 19 Aug 2019 06:40:54 +0200
From:   Sam Ravnborg <sam@...nborg.org>
To:     xinliang <z.liuxinliang@...ilicon.com>,
        John Stultz <john.stultz@...aro.org>
Cc:     John Stultz <john.stultz@...aro.org>, xuyiping@...ilicon.com,
        Rongrong Zou <zourongrong@...il.com>,
        Xinwei Kong <kong.kongxinwei@...ilicon.com>,
        Chen Feng <puck.chen@...ilicon.com>,
        lkml <linux-kernel@...r.kernel.org>,
        David Airlie <airlied@...ux.ie>,
        dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [RESEND][PATCH v3 00/26] drm: Kirin driver cleanups to prep for
 Kirin960 support

Hi Xinliang

> > As Maintainers can we please get some feedback from one of you.
> > Just an "OK to commit" would do it.
> > But preferably an ack or a review on the individual patches.
> 
> As I have done a pre-review and talked with the  author before sending out
> the patches.
> So, for this serial patches,
> Acked-by: Xinliang Liu <z.liuxinliang@...ilicon.com>

Thanks!
We all know how it is to be busy, especially when trying to keep up
after role changes.
Unless someone beats me, then I will apply tonight or tomorrow.

> > If the reality is that John is the Maintainer today,
> > then we should update MAINTAINERS to reflect this.
> 
> I am assuming you are talking about the kirin[1] drm driver not the hibmc[2]
> one, right?
> I really appreciate John's awesome work at kirin drm driver all the way.
> Honestly, after my work change from mobile to server years ago, I am always
> waiting for some guy who is stably working at kirin drm driver to take the
> maintenance work.
> John, surely is a such guy.  Please add up a patch to update the maintainer
> as John, if John agree so.  Then John can push the patch set to drm
> maintainer himself.
> *Note* that the maintainer patch should break hisilicon drivers into kirin
> and hibmc two parts, like bellow:
> 
> DRM DRIVERS FOR HISILICON HIBMC
> M:  Xinliang Liu <z.liuxinliang@...ilicon.com>
> ...
> F:  drivers/gpu/drm/hisilicon/hibmc
> ...
> 
> DRM DRIVERS FOR HISILICON KIRIN
> M:  John Stultz <john.stultz@...aro.org>
> ...
> F:  drivers/gpu/drm/hisilicon/kirin
> ...
> 
> [1] drivers/gpu/drm/hisilicon/kirin # for kirin mobile display driver
> [2] drivers/gpu/drm/hisilicon/hibmc # for server VGA driver

Hi John

Up to the challenge?
If yes then please consider to apply for commit rights to drm-misc-next.

And read:
https://drm.pages.freedesktop.org/maintainer-tools/index.html

See this to get an account:
https://www.freedesktop.org/wiki/AccountRequests/

You will need an ssh account for drm-misc-next as it is not (yet?)
gitlab enabled.

	Sam