linux-kernel - Re: [git pull] drm final fixes for 5.16

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]

Message-ID: <CAKMK7uE_89hiD=C4z9i_XBPCqCAnL1SzXbzHqwOrCphFZKtUWg@mail.gmail.com>
Date:   Mon, 10 Jan 2022 16:36:08 +0100
From:   Daniel Vetter <daniel.vetter@...ll.ch>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Dave Airlie <airlied@...il.com>,
        Alex Deucher <alexdeucher@...il.com>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm final fixes for 5.16

On Fri, Jan 7, 2022 at 6:42 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Thu, Jan 6, 2022 at 7:23 PM Dave Airlie <airlied@...il.com> wrote:
> >
> > There is only the amdgpu runtime pm regression fix in here.
>
> Thanks, from a quick test it works for me - the backlight actually
> does eventually go away.
>
> It does so only on the second time the monitors say "no signal, going
> to power save", but that has been true before too.
>
> So I think there's still some confusion in this area, but it might be
> elsewhere - who knows what Wayland and friends do. At least it doesn't
> look like a regression to me any more.

Well it's not a true fix, just a "go back to exact old behaviour, but
limited to relevant gpus for amdgpu only" so that i915 doesn't
regress. I think there's some more debug to do here and
Alex/Harry&team can look at leisure now :-)

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch