linux-kernel - Re: [git pull] drm for 5.18-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: <CAPM=9tx+YeOCBZ0WRcSMKTyUYr5ngySratZ0K8tmRZ0rCaFf8Q@mail.gmail.com>
Date:   Fri, 25 Mar 2022 13:00:57 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        LKML <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Chun-Kuang Hu <chunkuang.hu@...nel.org>
Subject: Re: [git pull] drm for 5.18-rc1

> FYI, this breaks the DT bindings. The relevant patches didn't get
> reviewed nor run thru automated testing because their encoding was
> 'charset=y'[1]. (While email clients seem to just ignore that
> encoding, patchwork and b4 do not.) linux-next is still broken and has
> been since Mar 2[2]. v2 of the fixes[3] have been posted since Mar 9,
> and still aren't in linux-next.
>
> It doesn't have to be fixed in this PR, but it needs to be fixed
> before rc1. Otherwise, no one can test their bindings using rc1. In
> general, there's no reason fixes need to wait until after rc1 as
> Chun-Kuang suggests[4].

With the conflicts that Linus merged, can we get this rebased onto
Linus merge, and submitted to him?

Otherwise Linus I sent you a fix for the fbdev in a separate pull.

Dave.