mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Qiang Yu <yuq825@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lima@lists.freedesktop.org
Subject: Re: [Lima] [PATCH -next] MAINTAINERS: mark lima mailing list as moderated
Date: Mon, 8 Apr 2019 15:45:54 +0200	[thread overview]
Message-ID: <763785ea-ab9d-8135-be8d-a9fb8c92884b@baylibre.com> (raw)
In-Reply-To: <CAKGbVbuT84tS=H9BeOC7OQ8usopqcYjBy5hoMDTzJbCy7KJStw@mail.gmail.com>

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 <rdunlap@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 <rdunlap@infradead.org>
    Cc: Qiang Yu <yuq825@gmail.com>
    Cc: dri-devel@lists.freedesktop.org
    Cc: lima@lists.freedesktop.org
    Signed-off-by: Qiang Yu <yuq825@gmail.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/9138d8e8-5390-0650-9bc3-050b869e978c@infradead.org
    Reviewed-by: Neil Armstrong <narmstrong@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 <yuq825@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 <yuq825@gmail.com> wrote:
>>>
>>> On Mon, Apr 8, 2019 at 8:00 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>>>
>>>> On 08/04/2019 03:37, Qiang Yu wrote:
>>>>> Looks good for me, patch is:
>>>>> Reviewed-by: Qiang Yu <yuq825@gmail.com>
>>>>
>>>> Also:
>>>> Reviewed-by: Neil Armstrong <narmstrong@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 <rdunlap@infradead.org> wrote:
>>>>>>
>>>>>> From: Randy Dunlap <rdunlap@infradead.org>
>>>>>>
>>>>>> Note that the lima mailing list is moderated.
>>>>>>
>>>>>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>>>>>> Cc: Qiang Yu <yuq825@gmail.com>
>>>>>> Cc: dri-devel@lists.freedesktop.org
>>>>>> Cc: lima@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 <yuq825@gmail.com>
>>>>>>  L:     dri-devel@lists.freedesktop.org
>>>>>> -L:     lima@lists.freedesktop.org
>>>>>> +L:     lima@lists.freedesktop.org (moderated for non-subscribers)
>>>>>>  S:     Maintained
>>>>>>  F:     drivers/gpu/drm/lima/
>>>>>>  F:     include/uapi/drm/lima_drm.h
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> lima mailing list
>>>>> lima@lists.freedesktop.org
>>>>> https://lists.freedesktop.org/mailman/listinfo/lima
>>>>>
>>>>


  reply	other threads:[~2019-04-08 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 19:12 Randy Dunlap
2019-04-08  1:37 ` Qiang Yu
2019-04-08  4:41   ` Randy Dunlap
2019-04-08 12:00   ` [Lima] " Neil Armstrong
2019-04-08 12:26     ` Qiang Yu
2019-04-08 12:40       ` Qiang Yu
2019-04-08 13:19         ` Qiang Yu
2019-04-08 13:45           ` Neil Armstrong [this message]
2019-04-08 14:31             ` Qiang Yu
2019-04-08 12:32 ` Qiang Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=763785ea-ab9d-8135-be8d-a9fb8c92884b@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lima@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=yuq825@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®