[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 25 Nov 2022 16:17:57 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lee Jones <lee@...nel.org>
Cc: arnd@...db.de, nathan@...nel.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
tzimmermann@...e.de, airlied@...il.com, daniel@...ll.ch,
ndesaulniers@...gle.com, trix@...hat.com, harry.wentland@....com,
sunpeng.li@....com, Rodrigo.Siqueira@....com,
alexander.deucher@....com, christian.koenig@....com,
Xinhui.Pan@....com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
On Fri, 25 Nov 2022 12:07:48 +0000 Lee Jones <lee@...nel.org> wrote:
> Since b339ec9c229aa ("kbuild: Only default to -Werror if COMPILE_TEST") WERROR
> now defaults to COMPILE_TEST meaning that it's enabled for allmodconfig
> builds. This leads to some interesting failures, each resolved in this set.
Oh, I get it. Clang. I'll tweak the above para to make that clearer.
cc:stable question still applies? How much trouble will these build
errors be causing people for the next N years?
> With this set applied, I am able to obtain a successful allmodconfig Arm build.
Powered by blists - more mailing lists