linux-kernel - Re: [Lima] [PATCH -next] MAINTAINERS: mark lima mailing list as moderated

Open Source and information security mailing list archives

Message-ID: <CAKGbVbuT84tS=H9BeOC7OQ8usopqcYjBy5hoMDTzJbCy7KJStw@mail.gmail.com>
Date:   Mon, 8 Apr 2019 21:19:17 +0800
From:   Qiang Yu <yuq825@...il.com>
To:     Neil Armstrong <narmstrong@...libre.com>,
        Daniel Vetter <daniel@...ll.ch>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>, lima@...ts.freedesktop.org
Subject: Re: [Lima] [PATCH -next] MAINTAINERS: mark lima mailing list as moderated

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"?)

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?

Thanks,
Qiang

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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives