linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for Dave Hansen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org,
	dave.hansen@linux.intel.com, mingo@kernel.org
Subject: [tip:x86/cleanups] x86/mpx: Remove selftests Makefile entry
Date: Mon, 22 Jul 2019 02:58:07 -0700	[thread overview]
Message-ID: <tip-48febc03e6c239d96f46d8b38d91863769fc18c8@git.kernel.org> (raw)
In-Reply-To: <20190705175318.784C233E@viggo.jf.intel.com>

Commit-ID:  48febc03e6c239d96f46d8b38d91863769fc18c8
Gitweb:     https://git.kernel.org/tip/48febc03e6c239d96f46d8b38d91863769fc18c8
Author:     Dave Hansen <dave.hansen@linux.intel.com>
AuthorDate: Fri, 5 Jul 2019 10:53:18 -0700
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Mon, 22 Jul 2019 11:54:56 +0200

x86/mpx: Remove selftests Makefile entry

MPX is being removed from the kernel due to a lack of support in the
toolchain going forward (gcc).

This is the smallest possible patch to fix some issues that have been
reported around running the MPX selftests.  It it would also have been part
of any removal series, it is offered first.

Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/20190705175318.784C233E@viggo.jf.intel.com

---
 tools/testing/selftests/x86/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/x86/Makefile b/tools/testing/selftests/x86/Makefile
index fa07d526fe39..3bc5b744e644 100644
--- a/tools/testing/selftests/x86/Makefile
+++ b/tools/testing/selftests/x86/Makefile
@@ -11,7 +11,7 @@ CAN_BUILD_X86_64 := $(shell ./check_cc.sh $(CC) trivial_64bit_program.c)
 CAN_BUILD_WITH_NOPIE := $(shell ./check_cc.sh $(CC) trivial_program.c -no-pie)
 
 TARGETS_C_BOTHBITS := single_step_syscall sysret_ss_attrs syscall_nt test_mremap_vdso \
-			check_initial_reg_state sigreturn iopl mpx-mini-test ioperm \
+			check_initial_reg_state sigreturn iopl ioperm \
 			protection_keys test_vdso test_vsyscall mov_ss_trap \
 			syscall_arg_fault
 TARGETS_C_32BIT_ONLY := entry_from_vm86 test_syscall_vdso unwind_vdso \

  reply	other threads:[~2019-07-22  9:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 17:53 [PATCH 0/3] [RFC] x86: start the MPX removal process Dave Hansen
2019-07-05 17:53 ` [PATCH 1/3] x86/mpx: remove selftests Makefile entry Dave Hansen
2019-07-22  9:58   ` tip-bot for Dave Hansen [this message]
2019-07-05 17:53 ` [PATCH 2/3] x86/mpx: remove selftests themselves Dave Hansen
2019-07-22  9:58   ` [tip:x86/cleanups] x86/mpx: Remove " tip-bot for Dave Hansen
2019-07-05 17:53 ` [PATCH 3/3] x86/mpx: remove MPX APIs Dave Hansen
2019-07-22  9:59   ` [tip:x86/cleanups] x86/mpx: Remove " tip-bot for Dave Hansen
2020-01-22 13:09 ` [PATCH 0/3] [RFC] x86: start the MPX removal process Borislav Petkov
2020-01-22 18:14   ` Dave Hansen
2020-01-23 11:23     ` Borislav Petkov

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-48febc03e6c239d96f46d8b38d91863769fc18c8@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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).