Hi,
On 08/04/2019 15:19, Qiang Yu wrote:
> Oh, I'm really sorry if I did something wrong to use:
> dim push-branch drm-misc-next
> (Should the committer just use "git push" not the "dim push-branch
> drm-misc-next"?)
I can see your commit just fine on drm-misc-next :
commit 6f61a82507c95f146c4e529d28ef7e5ac93242c9 (HEAD -> drm-misc-next,
narmstrong/for-linux-next, narmstrong/drm-misc-next)
Author: Randy Dunlap <rdun...@infradead.org>
Date: Sun Apr 7 12:12:10 2019 -0700
MAINTAINERS: mark lima mailing list as moderated
Note that the lima mailing list is moderated.
Signed-off-by: Randy Dunlap <rdun...@infradead.org>
Cc: Qiang Yu <yuq...@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Cc: l...@lists.freedesktop.org
Signed-off-by: Qiang Yu <yuq...@gmail.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/9138d8e8-5390-0650-9bc3-050b869e9...@infradead.org
Reviewed-by: Neil Armstrong <narmstr...@baylibre.com>
>
> Because I found the drm-tip repo has been updated also with
> a few commits that I can't find similar ones in the history.
>
> Could any maintainer help with this?
I also usually use "dim push-branch drm-misc-next", it would not accept
the push if HEAD changed upstream anyway.
Neil
>
> Thanks,
> Qiang
>
> On Mon, Apr 8, 2019 at 8:40 PM Qiang Yu <yuq...@gmail.com> wrote:
>>
>> Here's a question first time I use command:
>> dim push-branch drm-misc-next
>>
>> I see it updates both drm-misc-next and for-linux-next branch, is this
>> expected? What's the difference between drm-misc-next/drm-misc-next-fixes
>> and for-linux-next/for-linux-next-fixes?
>>
>> Thanks,
>> Qiang
>>
>> On Mon, Apr 8, 2019 at 8:26 PM Qiang Yu <yuq...@gmail.com> wrote:
>>>
>>> On Mon, Apr 8, 2019 at 8:00 PM Neil Armstrong <narmstr...@baylibre.com>
>>> wrote:
>>>>
>>>> On 08/04/2019 03:37, Qiang Yu wrote:
>>>>> Looks good for me, patch is:
>>>>> Reviewed-by: Qiang Yu <yuq...@gmail.com>
>>>>
>>>> Also:
>>>> Reviewed-by: Neil Armstrong <narmstr...@baylibre.com>
>>>>
>>>>>
>>>>> Should I apply this patch to drm-misc in this case? Or this patch will be
>>>>> submitted in other kernel tree and back merged to drm-misc?
>>>>
>>>> You can push it yourself on the drm-misc-next branch now.
>>>>
>>>> (Then you can reply to the original patch when you applied it)
>>>
>>> Thanks for the guidance. I'll push it soon.
>>>
>>> Regards,
>>> Qiang
>>>
>>>>
>>>> Neil
>>>>
>>>>>
>>>>> Regards,
>>>>> Qiang
>>>>>
>>>>> On Mon, Apr 8, 2019 at 3:12 AM Randy Dunlap <rdun...@infradead.org> wrote:
>>>>>>
>>>>>> From: Randy Dunlap <rdun...@infradead.org>
>>>>>>
>>>>>> Note that the lima mailing list is moderated.
>>>>>>
>>>>>> Signed-off-by: Randy Dunlap <rdun...@infradead.org>
>>>>>> Cc: Qiang Yu <yuq...@gmail.com>
>>>>>> Cc: dri-devel@lists.freedesktop.org
>>>>>> Cc: l...@lists.freedesktop.org
>>>>>> ---
>>>>>> MAINTAINERS | 2 +-
>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> --- mmotm-2019-0405-1828.orig/MAINTAINERS
>>>>>> +++ mmotm-2019-0405-1828/MAINTAINERS
>>>>>> @@ -5226,7 +5226,7 @@ F: Documentation/devicetree/bindings/dis
>>>>>> DRM DRIVERS FOR LIMA
>>>>>> M: Qiang Yu <yuq...@gmail.com>
>>>>>> L: dri-devel@lists.freedesktop.org
>>>>>> -L: l...@lists.freedesktop.org
>>>>>> +L: l...@lists.freedesktop.org (moderated for non-subscribers)
>>>>>> S: Maintained
>>>>>> F: drivers/gpu/drm/lima/
>>>>>> F: include/uapi/drm/lima_drm.h
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> lima mailing list
>>>>> l...@lists.freedesktop.org
>>>>> https://lists.freedesktop.org/mailman/listinfo/lima
>>>>>
>>>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
