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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Feb 2019 17:04:59 +0100
From:   Daniel Vetter <daniel@...ll.ch>
To:     Rob Clark <robdclark@...il.com>
Cc:     dri-devel <dri-devel@...ts.freedesktop.org>,
        Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sean Paul <seanpaul@...omium.org>,
        Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
        "David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] MAINTAINERS: update entry for drm/msm

On Wed, Feb 13, 2019 at 4:43 PM Rob Clark via dri-devel
<dri-devel@...ts.freedesktop.org> wrote:
>
> On Wed, Feb 13, 2019 at 10:28 AM Daniel Vetter <daniel@...ll.ch> wrote:
> >
> > On Wed, Feb 13, 2019 at 10:10:44AM -0500, Rob Clark via dri-devel wrote:
> > > We've moved the tree to a shared gitlab tree, so that Sean can help out
> > > with maintainer duties.
> > >
> > > Cc: Sean Paul <seanpaul@...omium.org>
> > > Signed-off-by: Rob Clark <robdclark@...il.com>
> > > ---
> > > I can include this patch in msm-next for v5.1, but wanted to get it
> > > ack'd on list
> >
> > Is the plan to also add this to dim, for full group maintainership fun?
> > It's more or less adding a few lines to nightly.conf and done (plus
> > everyone being ok with using the dim tooling).
>
> I think drm/msm is big enough, that it wouldn't make sense to move to
> drm-misc..  but possibly using the dim tooling could make sense.

This was about using the dim tooling, not about moving msm to
drm-misc. That indeed doesn't make much sense. And Sean already knows
that tooling. Plus you pretty much need a big script if you want to
add more committers (which imo you guys totally should), since
otherwise you spend up endless amounts of time training people on
trivial hiccups.
-Daniel

> BR,
> -R
>
> > -Daniel
> >
> > >
> > >  MAINTAINERS | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 9919840d54cd..2141a1b6653d 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -4838,10 +4838,11 @@ F:    Documentation/devicetree/bindings/display/multi-inno,mi0283qt.txt
> > >
> > >  DRM DRIVER FOR MSM ADRENO GPU
> > >  M:   Rob Clark <robdclark@...il.com>
> > > +M:   Sean Paul <sean@...rly.run>
> > >  L:   linux-arm-msm@...r.kernel.org
> > >  L:   dri-devel@...ts.freedesktop.org
> > >  L:   freedreno@...ts.freedesktop.org
> > > -T:   git git://people.freedesktop.org/~robclark/linux
> > > +T:   git https://gitlab.freedesktop.org/drm/msm.git
> > >  S:   Maintained
> > >  F:   drivers/gpu/drm/msm/
> > >  F:   include/uapi/drm/msm_drm.h
> > > --
> > > A
> > > 2.20.1
> > >
> > > _______________________________________________
> > > dri-devel mailing list
> > > dri-devel@...ts.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > http://blog.ffwll.ch
> _______________________________________________
> dri-devel mailing list
> dri-devel@...ts.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ