linux-kernel - Re: [git pull] drm for 5.11-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] [day] [month] [year] [list]

Date:   Mon, 14 Dec 2020 17:55:49 -0500
From:   Alex Deucher <alexdeucher@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Christian König <christian.koenig@....com>,
        Dave Airlie <airlied@...il.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        LKML <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm for 5.11-rc1

On Mon, Dec 14, 2020 at 5:45 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Mon, Dec 14, 2020 at 2:29 PM Alex Deucher <alexdeucher@...il.com> wrote:
> >
> > The relevant fixes are:
>
> Ok, I can confirm that applying those two patches gets my workstation
> working properly again.
>
> Would it be possible to get those submitted properly (or I can just
> take them as-is, but would like to get a "please just pick them
> directly")?
>
> I don't like to continue to do merges during the merge windows with a
> known broken base - it makes for a nightmare of bisection when you
> have multiple independent problems, and I assume this hits not just me
> but a lot of people with radeon/amdgpu graphics?

Yes, anyone using AMD GPUs will be affected.  The patches are already
in drm-misc, so they should show up in the next drm -fixes PR, but I
think it would be fine to pick them directly to fix support for
everyone using your tree.

Alex