From: "tip-bot2 for Brian Gerst" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Brian Gerst <brgerst@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Masahiro Yamada <masahiroy@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/entry] x86/syscalls: Don't adjust CFLAGS for syscall tables
Date: Tue, 25 May 2021 15:00:50 -0000 [thread overview]
Message-ID: <162195485062.29796.9940389426312997877.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210524181707.132844-4-brgerst@gmail.com>
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 48f7eee81cd53a94699d28959566b41a9dcac1d9
Gitweb: https://git.kernel.org/tip/48f7eee81cd53a94699d28959566b41a9dcac1d9
Author: Brian Gerst <brgerst@gmail.com>
AuthorDate: Mon, 24 May 2021 14:17:07 -04:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Tue, 25 May 2021 16:59:23 +02:00
x86/syscalls: Don't adjust CFLAGS for syscall tables
The syscall_*.c files only contain data (the syscall tables). There
is no need to adjust CFLAGS for tracing and stack protector since they
contain no code.
Signed-off-by: Brian Gerst <brgerst@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
Link: https://lore.kernel.org/r/20210524181707.132844-4-brgerst@gmail.com
---
arch/x86/entry/Makefile | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/x86/entry/Makefile b/arch/x86/entry/Makefile
index 94d2843..7fec5dc 100644
--- a/arch/x86/entry/Makefile
+++ b/arch/x86/entry/Makefile
@@ -8,14 +8,8 @@ UBSAN_SANITIZE := n
KCOV_INSTRUMENT := n
CFLAGS_REMOVE_common.o = $(CC_FLAGS_FTRACE)
-CFLAGS_REMOVE_syscall_64.o = $(CC_FLAGS_FTRACE)
-CFLAGS_REMOVE_syscall_32.o = $(CC_FLAGS_FTRACE)
-CFLAGS_REMOVE_syscall_x32.o = $(CC_FLAGS_FTRACE)
CFLAGS_common.o += -fno-stack-protector
-CFLAGS_syscall_64.o += -fno-stack-protector
-CFLAGS_syscall_32.o += -fno-stack-protector
-CFLAGS_syscall_x32.o += -fno-stack-protector
obj-y := entry_$(BITS).o thunk_$(BITS).o syscall_$(BITS).o
obj-y += common.o
prev parent reply other threads:[~2021-05-25 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 18:17 [PATCH 0/3] x86: Syscall table cleanups Brian Gerst
2021-05-24 18:17 ` [PATCH 1/3] x86/uml/syscalls: Remove array index from syscall initializers Brian Gerst
2021-05-25 11:22 ` Masahiro Yamada
2021-05-25 15:00 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2021-05-24 18:17 ` [PATCH 2/3] x86/syscalls: Remove -Wno-override-init for syscall tables Brian Gerst
2021-05-25 12:01 ` Masahiro Yamada
2021-05-25 15:00 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2021-05-24 18:17 ` [PATCH 3/3] x86/syscalls: Don't sdjust CFLAGS " Brian Gerst
2021-05-25 12:01 ` Masahiro Yamada
2021-05-25 15:00 ` tip-bot2 for Brian Gerst [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=162195485062.29796.9940389426312997877.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).