From: tip-bot for Nick Desaulniers <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
yamada.masahiro@socionext.com, ndesaulniers@google.com,
tglx@linutronix.de, hpa@zytor.com, richard@nod.at,
mingo@kernel.org, mingo@redhat.com, jdike@addtoit.com,
bp@suse.de
Subject: [tip:x86/build] x86/um/vdso: Drop implicit common-page-size linker flag
Date: Tue, 11 Dec 2018 05:25:00 -0800 [thread overview]
Message-ID: <tip-e4f752dda0de351efd198f438b68e743029da68a@git.kernel.org> (raw)
In-Reply-To: <20181206191231.192355-1-ndesaulniers@google.com>
Commit-ID: e4f752dda0de351efd198f438b68e743029da68a
Gitweb: https://git.kernel.org/tip/e4f752dda0de351efd198f438b68e743029da68a
Author: Nick Desaulniers <ndesaulniers@google.com>
AuthorDate: Mon, 10 Dec 2018 14:27:16 -0800
Committer: Borislav Petkov <bp@suse.de>
CommitDate: Tue, 11 Dec 2018 14:19:42 +0100
x86/um/vdso: Drop implicit common-page-size linker flag
GNU linker's -z common-page-size's default value is based on the target
architecture. arch/x86/um/vdso/Makefile sets it to the architecture
default, which is implicit and redundant. Drop it so that one more LLVM
build issue gets addressed.
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Richard Weinberger <richard@nod.at>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jeff Dike <jdike@addtoit.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-um@lists.infradead.org
Cc: x86-ml <x86@kernel.org>
Link: https://lkml.kernel.org/r/20181206191231.192355-1-ndesaulniers@google.com
---
arch/x86/um/vdso/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/um/vdso/Makefile b/arch/x86/um/vdso/Makefile
index 822ccdba93ad..bf94060fc06f 100644
--- a/arch/x86/um/vdso/Makefile
+++ b/arch/x86/um/vdso/Makefile
@@ -26,7 +26,7 @@ targets += vdso.so vdso.so.dbg vdso.lds $(vobjs-y)
CPPFLAGS_vdso.lds += -P -C
VDSO_LDFLAGS_vdso.lds = -m64 -Wl,-soname=linux-vdso.so.1 \
- -Wl,-z,max-page-size=4096 -Wl,-z,common-page-size=4096
+ -Wl,-z,max-page-size=4096
$(obj)/vdso.o: $(src)/vdso.S $(obj)/vdso.so
prev parent reply other threads:[~2018-12-11 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 19:12 [PATCH] x86/vdso: drop implicit common-page-size linker flag ndesaulniers
2018-12-06 20:29 ` Andy Lutomirski
2018-12-07 10:18 ` Borislav Petkov
2018-12-07 17:45 ` Nick Desaulniers
2018-12-07 17:52 ` Borislav Petkov
2018-12-07 18:00 ` Nick Desaulniers
2018-12-07 18:33 ` [tip:x86/urgent] x86/vdso: Drop " tip-bot for Nick Desaulniers
2018-12-11 13:12 ` [tip:x86/build] x86/um/vdso: " tip-bot for ndesaulniers@google.com
2018-12-11 17:39 ` Nick Desaulniers
2018-12-11 17:43 ` Richard Weinberger
2018-12-11 17:46 ` Borislav Petkov
2018-12-11 17:53 ` Nick Desaulniers
2018-12-11 18:05 ` Borislav Petkov
2018-12-11 19:08 ` Nick Desaulniers
2018-12-11 20:14 ` Richard Weinberger
2018-12-11 20:53 ` Borislav Petkov
2018-12-11 13:25 ` tip-bot for Nick Desaulniers [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=tip-e4f752dda0de351efd198f438b68e743029da68a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).