From: Andrew Morton <akpm@linux-foundation.org>
To: Lee Jones <lee@kernel.org>
Cc: arnd@arndb.de, nathan@kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
ndesaulniers@google.com, trix@redhat.com, harry.wentland@amd.com,
sunpeng.li@amd.com, Rodrigo.Siqueira@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
Date: Fri, 25 Nov 2022 16:17:57 -0800 [thread overview]
Message-ID: <20221125161757.73f96b3b90f4884509097352@linux-foundation.org> (raw)
In-Reply-To: <20221125120750.3537134-1-lee@kernel.org>
On Fri, 25 Nov 2022 12:07:48 +0000 Lee Jones <lee@kernel.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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Lee Jones <lee@kernel.org>
Cc: llvm@lists.linux.dev, arnd@arndb.de, sunpeng.li@amd.com,
ndesaulniers@google.com, dri-devel@lists.freedesktop.org,
Xinhui.Pan@amd.com, linux-kernel@vger.kernel.org,
nathan@kernel.org, amd-gfx@lists.freedesktop.org,
tzimmermann@suse.de, trix@redhat.com, alexander.deucher@amd.com,
Rodrigo.Siqueira@amd.com, christian.koenig@amd.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
Date: Fri, 25 Nov 2022 16:17:57 -0800 [thread overview]
Message-ID: <20221125161757.73f96b3b90f4884509097352@linux-foundation.org> (raw)
In-Reply-To: <20221125120750.3537134-1-lee@kernel.org>
On Fri, 25 Nov 2022 12:07:48 +0000 Lee Jones <lee@kernel.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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Lee Jones <lee@kernel.org>
Cc: arnd@arndb.de, nathan@kernel.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
ndesaulniers@google.com, trix@redhat.com, harry.wentland@amd.com,
sunpeng.li@amd.com, Rodrigo.Siqueira@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
Date: Fri, 25 Nov 2022 16:17:57 -0800 [thread overview]
Message-ID: <20221125161757.73f96b3b90f4884509097352@linux-foundation.org> (raw)
In-Reply-To: <20221125120750.3537134-1-lee@kernel.org>
On Fri, 25 Nov 2022 12:07:48 +0000 Lee Jones <lee@kernel.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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Lee Jones <lee@kernel.org>
Cc: llvm@lists.linux.dev, daniel@ffwll.ch, arnd@arndb.de,
sunpeng.li@amd.com, ndesaulniers@google.com,
dri-devel@lists.freedesktop.org, Xinhui.Pan@amd.com,
maarten.lankhorst@linux.intel.com, linux-kernel@vger.kernel.org,
mripard@kernel.org, nathan@kernel.org, harry.wentland@amd.com,
amd-gfx@lists.freedesktop.org, tzimmermann@suse.de,
trix@redhat.com, alexander.deucher@amd.com,
Rodrigo.Siqueira@amd.com, airlied@gmail.com,
christian.koenig@amd.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors
Date: Fri, 25 Nov 2022 16:17:57 -0800 [thread overview]
Message-ID: <20221125161757.73f96b3b90f4884509097352@linux-foundation.org> (raw)
In-Reply-To: <20221125120750.3537134-1-lee@kernel.org>
On Fri, 25 Nov 2022 12:07:48 +0000 Lee Jones <lee@kernel.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.
next prev parent reply other threads:[~2022-11-26 0:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 12:07 [PATCH v2 0/2] Fix a bunch of allmodconfig errors Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 12:07 ` [PATCH v2 1/2] drm/amdgpu: Temporarily disable broken Clang builds due to blown stack-frame Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 12:11 ` Arnd Bergmann
2022-11-25 12:11 ` Arnd Bergmann
2022-11-25 12:11 ` Arnd Bergmann
2022-11-28 5:52 ` Nathan Chancellor
2022-11-28 5:52 ` Nathan Chancellor
2022-11-28 5:52 ` Nathan Chancellor
2022-11-28 5:52 ` Nathan Chancellor
2022-11-25 12:07 ` [PATCH v2 2/2] Kconfig.debug: Provide a little extra FRAME_WARN leeway when KASAN is enabled Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 12:07 ` Lee Jones
2022-11-25 13:40 ` Lee Jones
2022-11-25 13:40 ` Lee Jones
2022-11-25 13:40 ` Lee Jones
2022-11-25 13:57 ` Arnd Bergmann
2022-11-25 13:57 ` Arnd Bergmann
2022-11-25 13:57 ` Arnd Bergmann
2022-11-28 5:53 ` Nathan Chancellor
2022-11-28 5:53 ` Nathan Chancellor
2022-11-28 5:53 ` Nathan Chancellor
2022-11-28 5:53 ` Nathan Chancellor
2022-11-26 0:13 ` [PATCH v2 0/2] Fix a bunch of allmodconfig errors Andrew Morton
2022-11-26 0:13 ` Andrew Morton
2022-11-26 0:13 ` Andrew Morton
2022-11-26 0:13 ` Andrew Morton
2022-11-28 7:47 ` Lee Jones
2022-11-28 7:47 ` Lee Jones
2022-11-28 7:47 ` Lee Jones
2022-11-28 7:47 ` Lee Jones
2022-11-26 0:17 ` Andrew Morton [this message]
2022-11-26 0:17 ` Andrew Morton
2022-11-26 0:17 ` Andrew Morton
2022-11-26 0:17 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221125161757.73f96b3b90f4884509097352@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnd@arndb.de \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sunpeng.li@amd.com \
--cc=trix@redhat.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.