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: <CAK7LNASCFVxGV0e1DbnJzrtRJs_iuMsL6Q-2oxpoRMaSK5U1ZA@mail.gmail.com>
Date:   Thu, 13 Oct 2022 07:34:21 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Alex Deucher <alexander.deucher@....com>,
        Dmytro Laktyushkin <Dmytro.Laktyushkin@....com>,
        Jun Lei <Jun.Lei@....com>,
        Harry Wentland <harry.wentland@....com>,
        Rodrigo Siqueira <Rodrigo.Siqueira@....com>,
        Zeng Heng <zengheng4@...wei.com>,
        Wenjing Liu <Wenjing.Liu@....com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree

On Thu, Oct 13, 2022 at 7:17 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
>
> Exposed by commit
>
>   61168a974a16 ("Makefile: add implicit enum-conversion check for compile build")
>
> We don't add compiler flags that produce more warnings/errors without
> first fixing the known problems.  This was the example of what would
> happen that was cited in the commit message.
>
> I have used the kbuild tree from next-20221012 for today.
>
> Is this new stuff really destined for 6.1?
>
> The actual error was caused by commits
>
>   5fc11598166d ("drm/amd/display: expand dml structs")
>   d478667253f9 ("drm/amd/display: use odm combine for YCbCr420 timing with h_active greater than 4096")
>
> which entered Linus' tree during this merge window.
>
> --
> Cheers,
> Stephen Rothwell


Or, if it is not too late,
can you revert only commit 61168a974a16?


I will drop it for tomorrow's linux-next.




-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ