From: Darren Hart <dvhart@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Darren Hart <dvhart@linux.intel.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
linux-api@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Davidlohr Bueso <dave@stgolabs.net>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: [PATCH 4/5] selftest: Add futex tests to the top-level Makefile
Date: Fri, 27 Mar 2015 15:17:44 -0700 [thread overview]
Message-ID: <dbaaa8da375e3192733ac7f7c7d92e1cfaa14c87.1427493640.git.dvhart@linux.intel.com> (raw)
In-Reply-To: <597c9eabcac5da9456d6cfd6de9117591d73385e.1427493640.git.dvhart@linux.intel.com>
In-Reply-To: <cover.1427493640.git.dvhart@linux.intel.com>
Enable futex tests to be built and run with the make kselftest and
associated targets.
Most of the tests require escalated privileges. These return ERROR, and
run.sh continues.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: linux-api@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
---
tools/testing/selftests/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile
index 9af1df2..6eef08a 100644
--- a/tools/testing/selftests/Makefile
+++ b/tools/testing/selftests/Makefile
@@ -4,6 +4,7 @@ TARGETS += efivarfs
TARGETS += exec
TARGETS += firmware
TARGETS += ftrace
+TARGETS += futex
TARGETS += kcmp
TARGETS += memfd
TARGETS += memory-hotplug
--
2.1.4
next prev parent reply other threads:[~2015-03-27 22:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 22:17 [GIT PULL] selftest: Add futex functional tests Darren Hart
2015-03-27 22:17 ` [PATCH 1/5] selftests: " Darren Hart
2015-05-06 17:28 ` Shuah Khan
2015-05-06 18:04 ` Darren Hart
2015-03-27 22:17 ` [PATCH 2/5] selftest/futex: Update Makefile to use lib.mk Darren Hart
2015-03-29 23:49 ` Michael Ellerman
2015-03-30 16:31 ` Darren Hart
2015-03-31 23:28 ` Michael Ellerman
2015-03-27 22:17 ` [PATCH 3/5] selftest/futex: Increment ksft pass and fail counters Darren Hart
2015-03-27 22:17 ` Darren Hart [this message]
2015-03-27 22:17 ` [PATCH 5/5] kselftest: Add exit code defines Darren Hart
2015-03-27 22:59 ` Michael Ellerman
2015-03-27 23:09 ` Darren Hart
2015-03-29 23:44 ` Michael Ellerman
2015-03-30 16:26 ` Darren Hart
2015-03-30 16:30 ` Peter Zijlstra
[not found] ` <551ABE00.9050003@osg.samsung.com>
2015-03-31 16:24 ` [GIT PULL] selftest: Add futex functional tests Darren Hart
2015-03-31 16:37 ` Shuah Khan
2015-04-08 4:12 ` Darren Hart
2015-04-09 5:41 ` Shuah Khan
2015-04-09 5:44 ` Darren Hart
2015-05-06 18:34 ` Davidlohr Bueso
2015-05-08 22:09 [PATCH 1/5] selftests: " Darren Hart
2015-05-08 22:09 ` [GIT PULL v2] selftest: " Darren Hart
2015-05-08 22:09 ` [PATCH 4/5] selftest: Add futex tests to the top-level Makefile Darren Hart
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=dbaaa8da375e3192733ac7f7c7d92e1cfaa14c87.1427493640.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=shuahkh@osg.samsung.com \
--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).