Re: [RESEND][PATCH v3 00/26] drm: Kirin driver cleanups to prep for Kirin960 support
From: John Stultz
Date: Mon Aug 19 2019 - 19:25:37 EST
On Sun, Aug 18, 2019 at 9:40 PM Sam Ravnborg <sam@xxxxxxxxxxxx> wrote:
> > > 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@xxxxxxxxxxxxx>
> 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 drm driver not the hibmc
> > 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@xxxxxxxxxxxxx>
> > ...
> > F: drivers/gpu/drm/hisilicon/hibmc
> > ...
> > DRM DRIVERS FOR HISILICON KIRIN
> > M: John Stultz <john.stultz@xxxxxxxxxx>
> > ...
> > F: drivers/gpu/drm/hisilicon/kirin
> > ...
> >  drivers/gpu/drm/hisilicon/kirin # for kirin mobile display driver
> >  drivers/gpu/drm/hisilicon/hibmc # for server VGA driver
> Hi John
> Up to the challenge?
I guess if necessary, though I don't believe myself to be a great maintainer.
Though I do have the hardware, am regularly are testing on it, and
maintain a tree of patches to keep it working, so I can validate basic
correctness and handle patch wrangling.
> If yes then please consider to apply for commit rights to drm-misc-next.
> And read:
> See this to get an account:
> You will need an ssh account for drm-misc-next as it is not (yet?)
> gitlab enabled.
I'll try to find some time to read through the above and apply.