From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F204EC43334 for ; Fri, 24 Jun 2022 21:05:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231139AbiFXVFn (ORCPT ); Fri, 24 Jun 2022 17:05:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230284AbiFXVFm (ORCPT ); Fri, 24 Jun 2022 17:05:42 -0400 Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E7C327FD14 for ; Fri, 24 Jun 2022 14:05:40 -0700 (PDT) Received: by mail-wm1-x32f.google.com with SMTP id l2-20020a05600c4f0200b0039c55c50482so3984511wmq.0 for ; Fri, 24 Jun 2022 14:05:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=4FBq55ALNoB8I9/Jp2eahFZ3TVuZO8zAHamAFfwJTA4=; b=jtNLzbazAZ3Ty+PCe4NJUDW5r9cbkHlRd8h2mbV7+waX1Tx9erQtwlu2e8BUxesIDH SpaHCfUHUYE9Gcjqbo0B/IDMs/JrP3lo3//ZjLcKnRD7/2NuKlxlUOPrugPQ8PeHKwme wzVoLofv+/w69KJivy77K+FdWGQ9xTFTuR8C0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=4FBq55ALNoB8I9/Jp2eahFZ3TVuZO8zAHamAFfwJTA4=; b=41FUHV4iKPbrdz/faQsSTqDObVJdZJ2M75Z7Mn1wPElAsgTQqVy50BYE3sxFsm3gfD aSsev/6emMlnXh94t49REo4ZaAIPqAYUKrw+6n7C+MopRVCssjdQDPy16rZ9bJ7U5WNe UNm2XkHiB96geFy0Mj6obLVZXeOlgZJrfdyymijtx+qAIjdKJ9Zf7HfHAM8ht7hKUBZh jvcyxMNZqrTq0EGXZgl5qnEYDP5LQhLFCTqMJOHRV7ueU5qbAw3TBEVMVUieH89UES4R HGUuYCVTpGjKqgNeHOmEjX9oR88B1qIU9SyIvRGCiWJLEf5tX3MMVkZSp+6ifEVnN0gL KonQ== X-Gm-Message-State: AJIora/EI1Q+kScADPqgRlq7wBArtEaeBKVpIpLG9ONsKkm3mye8GCqL YxPSkmf2YUlXaC0BXwTHsLTurg== X-Google-Smtp-Source: AGRyM1s3Pl4EVQvFKsoBwid6w18frt80sinR1W0DhYBmiX4lMtmHCpKONBuPPCGUsGyEmAfWWb+3qw== X-Received: by 2002:a05:600c:3553:b0:39c:63a3:f54a with SMTP id i19-20020a05600c355300b0039c63a3f54amr989149wmq.61.1656104739492; Fri, 24 Jun 2022 14:05:39 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id i6-20020a05600c354600b003974a00697esm8995188wmq.38.2022.06.24.14.05.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jun 2022 14:05:39 -0700 (PDT) Date: Fri, 24 Jun 2022 23:05:37 +0200 From: Daniel Vetter To: Dmitry Baryshkov Cc: Stephen Rothwell , linux-next@vger.kernel.org, freedreno , linux-kernel@vger.kernel.org, dri-devel Subject: Re: Please add another drm/msm tree to the linux-next Message-ID: Mail-Followup-To: Dmitry Baryshkov , Stephen Rothwell , linux-next@vger.kernel.org, freedreno , linux-kernel@vger.kernel.org, dri-devel References: <5dbc0159-cb33-db5b-20cc-05f3027af15e@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5dbc0159-cb33-db5b-20cc-05f3027af15e@linaro.org> X-Operating-System: Linux phenom 5.10.0-8-amd64 Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org 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