Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
On Fri, 25 Nov 2022 12:07:48 + Lee Jones 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.
Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
On Fri, 25 Nov 2022 12:07:48 + Lee Jones 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.
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 + Lee Jones 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 [李琼斯]
[PATCH v2 0/2] Fix a bunch of allmodconfig errors
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.
With this set applied, I am able to obtain a successful allmodconfig Arm build.
v1 => v2:
- Remove superfluous change (these two override it)
- Mark only DRM_AMD_DC ("the new display engine) as Broken
- Change logic to only *include* working arches, not *preclude* them
Lee Jones (2):
drm/amdgpu: Temporarily disable broken Clang builds due to blown
stack-frame
Kconfig.debug: Provide a little extra FRAME_WARN leeway when KASAN is
enabled
drivers/gpu/drm/amd/display/Kconfig | 7 +++
lib/Kconfig.debug | 1 +
2 files changed, 8 insertions(+)
--
2.38.1.584.g0f3c55d4c2-goog
