linux-kernel - Re: [BUG] allmodconfig build error in next-20240108

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]

Date: Wed, 10 Jan 2024 09:21:14 -0600
From: Lucas De Marchi <lucas.demarchi@...el.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>
CC: "Paul E. McKenney" <paulmck@...nel.org>, Stephen Rothwell
	<sfr@...b.auug.org.au>, <linux-kernel@...r.kernel.org>,
	<intel-xe@...ts.freedesktop.org>
Subject: Re: [BUG] allmodconfig build error in next-20240108

On Wed, Jan 10, 2024 at 05:18:11PM +0200, Jani Nikula wrote:
>On Wed, 10 Jan 2024, Lucas De Marchi <lucas.demarchi@...el.com> wrote:
>> [ This particular warning is broken on GCC11. In future changes it will
>>    be moved to the normal C flags in the top level Makefile (out of
>>    Makefile.extrawarn), but accounting for the compiler support. Just
>>    remove it out of xe's forced extra warnings for now ]
>> Signed-off-by: Lucas De Marchi <lucas.demarchi@...el.com>
>>
>> would you mind if I extend it to drivers/gpu/drm/i915/Makefile
>> in the same commit or would you prefer a separate one?
>
>I think I'd prefer separate patches for i915 and xe. And just remove the
>line instead of subdir-ccflags-$(call gcc-min-version, 120000) as
>linux-next handles it properly in the top level Makefile.

yes, this is what this patch is doing, just removing the line.

Lucas De Marchi.

>
>BR,
>Jani.
>
>
>
>-- 
>Jani Nikula, Intel