From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: DRM pull for v5.3-rc1 Date: Mon, 15 Jul 2019 17:57:30 +0000 Message-ID: <20190715175726.GC5043@mellanox.com> References: <20190715122924.GA15202@mellanox.com> <20190715150402.GD15202@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Language: en-US Content-ID: <235CAD9B97456C44AD6D8293CD6612A1@eurprd05.prod.outlook.com> Sender: linux-kernel-owner@vger.kernel.org To: Daniel Vetter Cc: Dave Airlie , Linus Torvalds , dri-devel , LKML , Andrew Morton , Jerome Glisse , Thomas Hellstrom , Stephen Rothwell List-Id: dri-devel@lists.freedesktop.org On Mon, Jul 15, 2019 at 07:53:06PM +0200, Daniel Vetter wrote: > > So, I'll put it on a topic and send you two a note next week to decide > > if you want to merge it or not. I'm really unclear how nouveau's and > > AMD's patchflow works.. >=20 > DRM is 2-level for pretty much everything. First it lands in a driver > tree (or a collectiv of drivers, like in drm-misc). Then those send > pull requests to drm.git for integration. Busy trees do that every 1-2 > weeks (e.g. amdgpu), slower trees once per merge window (e.g. nouveau) > for drm-next, similar for drm-fixes. The DRM part seems logical - it is how the AMD GPU and nouveau git trees trees work that I don't know. I heard that neither could take in a stable topic branch? Jason