From: Nathan Chancellor <natechancellor@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Nick Desaulniers <ndesaulniers@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] Makefile: Add '-fno-builtin-bcmp' to CLANG_FLAGS
Date: Mon, 25 Mar 2019 07:02:36 -0700 [thread overview]
Message-ID: <20190325140236.GB13100@archlinux-ryzen> (raw)
In-Reply-To: <20190325003834.2F24E2133F@mail.kernel.org>
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
prev parent reply other threads:[~2019-03-25 14:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:52 [PATCH] Makefile: Add '-fno-builtin-bcmp' to CLANG_FLAGS Nathan Chancellor
2019-03-12 22:55 ` Nick Desaulniers
2019-03-13 8:13 ` Rasmus Villemoes
2019-03-13 10:58 ` Masahiro Yamada
2019-03-13 13:44 ` Nathan Chancellor
2019-03-13 13:48 ` Arnd Bergmann
2019-03-13 15:32 ` Nathan Chancellor
2019-03-13 17:21 ` Nick Desaulniers
2019-03-13 17:27 ` Nick Desaulniers
2019-03-13 18:02 ` [PATCH] lib/string.c: implement a basic bcmp Nick Desaulniers
2019-03-13 18:11 ` Nick Desaulniers
2019-03-13 18:17 ` [PATCH v2] " Nick Desaulniers
2019-03-13 18:40 ` Steven Rostedt
2019-03-13 18:51 ` Nick Desaulniers
2019-03-13 19:01 ` Steven Rostedt
2019-03-13 19:34 ` Rasmus Villemoes
2019-03-13 20:12 ` Steven Rostedt
2019-03-13 20:37 ` [PATCH v3] " Nick Desaulniers
2019-03-13 21:03 ` Steven Rostedt
2019-03-13 21:13 ` [PATCH v4] " Nick Desaulniers
2019-03-14 3:15 ` Nathan Chancellor
2019-03-14 5:00 ` Masahiro Yamada
2019-03-14 8:33 ` Andy Shevchenko
2019-03-14 9:57 ` David Laight
2019-03-14 11:07 ` Rasmus Villemoes
2019-03-21 2:11 ` Andrew Morton
2019-03-21 17:02 ` Nick Desaulniers
2019-03-21 17:20 ` Nick Desaulniers
2019-03-21 21:05 ` Andrew Morton
2019-03-13 19:38 ` [PATCH] Makefile: Add '-fno-builtin-bcmp' to CLANG_FLAGS Arnd Bergmann
[not found] ` <20190325003834.2F24E2133F@mail.kernel.org>
2019-03-25 14:02 ` Nathan Chancellor [this message]
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=20190325140236.GB13100@archlinux-ryzen \
--to=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox