Re: [GIT PULL] drm-hisilicon-next

From: Daniel Vetter <daniel@ffwll.ch>
To: Xinliang Liu <xinliang.liu@linaro.org>
Cc: Peter Griffin <peter.griffin@linaro.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Guodong Xu <guodong.xu@linaro.org>
Subject: Re: [GIT PULL] drm-hisilicon-next
Date: Tue, 29 Aug 2017 15:57:35 +0200	[thread overview]
Message-ID: <CAKMK7uFSSyU1wOe9MVbrzj21MpYoOZf4rL9f0_prp_0RF-kaVQ@mail.gmail.com> (raw)
In-Reply-To: <CAGd==06Qz4kBxR15kjJfeY2aDDSStgugoRd4wkUMBPzM7by1uA@mail.gmail.com>

On Tue, Aug 29, 2017 at 11:54 AM, Xinliang Liu <xinliang.liu@linaro.org> wrote:
> Hi Dave,
>
> On 29 August 2017 at 16:32, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Tue, Aug 29, 2017 at 10:46:33AM +0800, Xinliang Liu wrote:
>>> Hi Dave,
>>> One fix for next.
>>> Sorry for late pull request. If it can't catch this round, will resend
>>> on next round.
>>
>> drm-misc is always open for features, which makes this a lot simpler. Just
>> in case you want to reconsider moving hisilicon into drm-misc :-)
>
> If  moving hisilicon into drm-misc make things simpler, I would like to do it.
> Just clarify how to do this:
> I just need to change the git tree to drm-misc? I see a lot of drm
> drivers maintainers set the their git tree to
> git://anongit.freedesktop.org/drm/drm-misc.
> The means to be an drm-misc maintainer, right?
> I wonder how new driver specific features/fixes patches go into drm-misc then?
>  Do I need to send a pull request to  drm-misc tree. I don't think I
> have a write permission to drm-misc tree.

You'll need to become drm-misc committer, and patches are pushed
directly using the scripts we have:

https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html

Here's the rules for how drm-misc works:

https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html

drm-misc is essentially a service provided to take care of some of the
maintainer chores, but review and patch merging still needs to be done
by the individual driver owners (i.e. we won't take a new driver
without a committer for it).

Cheers, Daniel

>
> Best,
> Xinliang
>
>> -Daniel
>>
>>>
>>>
>>> Best,
>>> Xinliang
>>>
>>>
>>> The following changes since commit 7846b12fe0b5feab5446d892f41b5140c1419109:
>>>
>>>   Merge branch 'drm-vmwgfx-next' of
>>> git://people.freedesktop.org/~syeh/repos_linux into drm-next
>>> (2017-08-29 10:38:14 +1000)
>>>
>>> are available in the git repository at:
>>>
>>>
>>>   git@github.com:xin3liang/linux.git tags/drm-hisilicon-next-2017-08-29
>>>
>>> for you to fetch changes up to 834fe0f6023a4fad68612dbbe93866c4df32142e:
>>>
>>>   drm/hisilicon: Ensure LDI regs are properly configured. (2017-08-29
>>> 10:17:18 +0800)
>>>
>>> ----------------------------------------------------------------
>>> hisilicon-drm-next
>>>
>>> ----------------------------------------------------------------
>>> Peter Griffin (1):
>>>       drm/hisilicon: Ensure LDI regs are properly configured.
>>>
>>>  drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 3 +++
>>>  1 file changed, 3 insertions(+)
>>> _______________________________________________
>>> dri-devel mailing list
>>> dri-devel@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> http://blog.ffwll.ch

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel