Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <9138d8e8-5390-0650-9bc3-050b869e978c@infradead.org>
 <CAKGbVbugBGrxfHm3k7WB+FS_O-Bjj9PyKrSDteTy1sra=nd6cw@mail.gmail.com>
 <054b9d43-cf4e-057d-132d-7c1758956595@baylibre.com> <CAKGbVbtok8RUzDqw=WShAHoiLqWLaKA8coKhcW5EPrsHCO89pA@mail.gmail.com>
 <CAKGbVbtpNKxUDRM9nE05gBuS5jwO68wHh0Uq2NsdYX6pdFtxYw@mail.gmail.com>
 <CAKGbVbuT84tS=H9BeOC7OQ8usopqcYjBy5hoMDTzJbCy7KJStw@mail.gmail.com> <763785ea-ab9d-8135-be8d-a9fb8c92884b@baylibre.com>
In-Reply-To: <763785ea-ab9d-8135-be8d-a9fb8c92884b@baylibre.com>
From:   Qiang Yu <yuq825@gmail.com>
Date:   Mon, 8 Apr 2019 22:31:49 +0800
Message-ID: <CAKGbVbuuhb36mrTuNroQxBtdUswATzLWTAg+1roVbEhPdoAc_g@mail.gmail.com>
Subject: Re: [Lima] [PATCH -next] MAINTAINERS: mark lima mailing list as moderated
To:     Neil Armstrong <narmstrong@baylibre.com>
Cc:     Daniel Vetter <daniel@ffwll.ch>,
        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
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Apr 8, 2019 at 9:45 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>
> 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.

How about the drm-tip repo in your case? Will it be updated also after the
command?
https://cgit.freedesktop.org/drm-tip/

I see there're a couple of merge commits by me at the top of drm-tip which
push in many code from other branches and add a new file integration-manifest.
I can't find similar commits in the history, so worry I've done something wrong.

Regards,
Qiang

>
> 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
> >>>>>
> >>>>
>