linux-kernel - Re: DRM pull for v5.3-rc1

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]

Message-ID: <20190715175726.GC5043@mellanox.com>
Date:   Mon, 15 Jul 2019 17:57:30 +0000
From:   Jason Gunthorpe <jgg@...lanox.com>
To:     Daniel Vetter <daniel.vetter@...ll.ch>
CC:     Dave Airlie <airlied@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Jerome Glisse <jglisse@...hat.com>,
        Thomas Hellstrom <thellstrom@...are.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: DRM pull for v5.3-rc1

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..
> 
> 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