[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YrYnIY2s2Nj5C66N@phenom.ffwll.local>
Date: Fri, 24 Jun 2022 23:05:37 +0200
From: Daniel Vetter <daniel@...ll.ch>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org,
freedreno <freedreno@...ts.freedesktop.org>,
linux-kernel@...r.kernel.org,
dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: Please add another drm/msm tree to the linux-next
On Wed, Jun 15, 2022 at 05:19:42PM +0300, Dmitry Baryshkov wrote:
> Hi Stephen,
>
> I would appreciate if you could add
>
> https://gitlab.freedesktop.org/lumag/msm.git msm-next-lumag
>
> to the linux-next tree.
>
> This tree is a part of drm/msm maintenance structure. As a co-maintainer I
> collect and test display patches, while Rob concenctrates on GPU part of the
> driver. Later during the release cycle these patchesare pulled by Rob Clark
> directly into msm-next.
>
> During last cycle Rob suggested adding this tree to the linux-next effort,
> so that the patches receive better integration testing during the Linux
> development cycle.
Have you guys thought of group maintainering? Single point of failure
trees freak me out a bit, it tends to build silos pretty hard. Simplest
path is to just toss it all into drm-misc, but at least have one tree for
your driver. Building new single maintainer silos after I've run around
for years collecting them all is rather meh.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists