On Mon, Mar 25, 2019 at 12:38:33AM +0000, Sasha Levin wrote:

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.0.3, v4.19.30, v4.14.107, v4.9.164, v4.4.176, v3.18.136.

v5.0.3: Build OK! v4.19.30: Build OK! v4.14.107: Build OK! v4.9.164: Build OK! v4.4.176: Failed to apply! Possible dependencies: 238bcbc4e07f ("kbuild: consolidate Clang compiler flags") dbe27a002ef8 ("kbuild: add -no-integrated-as Clang option unconditionally")

v3.18.136: Failed to apply! Possible dependencies: 238bcbc4e07f ("kbuild: consolidate Clang compiler flags") 35288e30ebca ("Kbuild: fix file name in comment about extra gcc checks") 5631d9c42985 ("kbuild: Fix clang detection") 665d92e38f65 ("kbuild: do not add $(call ...) to invoke cc-version or cc-fullversion") 785f11aa595b ("kbuild: Add better clang cross build support") 92d6cf2dab83 ("powerpc: Don't use -mno-strict-align on clang") a37c45cd82e6 ("kbuild: clang: add -no-integrated-as to KBUILD_[AC]FLAGS") ae6b289a3789 ("kbuild: Set KBUILD_CFLAGS before incl. arch Makefile") bb3f38c3c5b7 ("kbuild: clang: fix build failures with sparse check") bfb38988c51e ("kbuild: clang: Disable 'address-of-packed-member' warning") dd33c03b18b3 ("kbuild: fix cc-ifversion macro") e79c8385c878 ("powerpc: Don't do gcc version checks if we're building with clang") ee4eb20dbce9 ("Makefile: Fix detection of clang when cross-compiling") ef8c4ed9db80 ("kbuild: allow to use GCC toolchain not in Clang search path")

How should we proceed with this patch?

-- Thanks, Sasha

Hi Sasha,

This patch will not be picked up, Nick's patch is a much better fix, which should apply cleanly to all stable branches after it makes it into mainline.

https://lore.kernel.org/lkml/20190313211335.165605-1-ndesaulniers@google.com...

Thanks for letting us know! Nathan