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>
In-Reply-To: <CAKGbVbtok8RUzDqw=WShAHoiLqWLaKA8coKhcW5EPrsHCO89pA@mail.gmail.com>
From:   Qiang Yu <yuq825@gmail.com>
Date:   Mon, 8 Apr 2019 20:40:30 +0800
Message-ID: <CAKGbVbtpNKxUDRM9nE05gBuS5jwO68wHh0Uq2NsdYX6pdFtxYw@mail.gmail.com>
Subject: Re: [Lima] [PATCH -next] MAINTAINERS: mark lima mailing list as moderated
To:     Neil Armstrong <narmstrong@baylibre.com>
Cc:     Randy Dunlap <rdunlap@infradead.org>,
        Daniel Vetter <daniel@ffwll.ch>,
        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

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