[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y4RnesCbA0yOFI8/@google.com>
Date: Mon, 28 Nov 2022 07:47:06 +0000
From: Lee Jones <lee@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.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, Andrew Morton wrote:
> 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.
>
> I'm not sure who this patchset is aimed at, so I'll take my usual
> approach of grabbing it and seeing who complains.
>
> > With this set applied, I am able to obtain a successful allmodconfig Arm build.
>
> b339ec9c229aa is a year old and I've been doing arm allmodconfig for
> ever. What am I missing here?
>
> A broken arm allmodconfig is pretty irritating - I'm thinking that a
> fix should be backported into -stable kernels. But I'm clearly missing
> something here.
I will be taking these through all applicable Stable kernels.
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists