[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1907241233240.1972@nanos.tec.linutronix.de>
Date: Wed, 24 Jul 2019 12:35:46 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Nick Desaulniers <ndesaulniers@...gle.com>
cc: mingo@...hat.com, bp@...en8.de, peterz@...radead.org,
clang-built-linux@...glegroups.com, linux-kernel@...r.kernel.org,
yamada.masahiro@...ionext.com, stable@...r.kernel.org,
Vaibhav Rustagi <vaibhavrustagi@...gle.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Subject: Re: [PATCH v3 2/2] x86/purgatory: use CFLAGS_REMOVE rather than
reset KBUILD_CFLAGS
On Tue, 23 Jul 2019, Nick Desaulniers wrote:
> +ifdef CONFIG_FUNCTION_TRACER
> +CFLAGS_REMOVE_sha256.o += $(CC_FLAGS_FTRACE)
> +CFLAGS_REMOVE_purgatory.o += $(CC_FLAGS_FTRACE)
> +CFLAGS_REMOVE_string.o += $(CC_FLAGS_FTRACE)
> +CFLAGS_REMOVE_kexec-purgatory.o += $(CC_FLAGS_FTRACE)
Nit. Can you please make that tabular?
CFLAGS_REMOVE_sha256.o += $(CC_FLAGS_FTRACE)
CFLAGS_REMOVE_purgatory.o += $(CC_FLAGS_FTRACE)
CFLAGS_REMOVE_string.o += $(CC_FLAGS_FTRACE)
CFLAGS_REMOVE_kexec-purgatory.o += $(CC_FLAGS_FTRACE)
The above confused my pattern recognition engine :)
Thanks,
tglx
Powered by blists - more mailing lists