From: Michael Ellerman <mpe@ellerman.id.au>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
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: Re: [PATCH 2/5] selftest/futex: Update Makefile to use lib.mk
Date: Mon, 30 Mar 2015 10:49:38 +1100 [thread overview]
Message-ID: <1427672978.4218.3.camel@ellerman.id.au> (raw)
In-Reply-To: <95d599bc531666252f8e3f4e467d5f94af2a7ad2.1427493640.git.dvhart@linux.intel.com>
On Fri, 2015-03-27 at 15:17 -0700, Darren Hart wrote:
> Adapt the futextest Makefiles to use lib.mk macros for RUN_TESTS and
> EMIT_TESTS. For now, we reuse the run.sh mechanism provided by
> futextest. This doesn't provide the standard selftests: [PASS|FAIL]
> format, but the tests provide very similar output already.
>
> This results in the run_kselftest.sh script for futexes including a
> single line: ./run.sh
>
> 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/futex/Makefile | 21 +++++++++++++++++++++
> tools/testing/selftests/futex/functional/Makefile | 4 ++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/tools/testing/selftests/futex/Makefile b/tools/testing/selftests/futex/Makefile
> index 8629187..6a17529 100644
> --- a/tools/testing/selftests/futex/Makefile
> +++ b/tools/testing/selftests/futex/Makefile
> @@ -1,8 +1,29 @@
> SUBDIRS := functional
>
> +TEST_PROGS := run.sh
> +
> .PHONY: all clean
lib.mk defines all & clean as PHONY for you.
> all:
> for DIR in $(SUBDIRS); do $(MAKE) -C $$DIR $@ ; done
>
> +include ../lib.mk
> +
> +override define RUN_TESTS
> + ./run.sh
> +endef
Do you need to do this override? The standard logic should work AFAICS, or do
you not want the echo logic?
> +override define INSTALL_RULE
> + mkdir -p $(INSTALL_PATH)
> + install -t $(INSTALL_PATH) $(TEST_PROGS) $(TEST_PROGS_EXTENDED) $(TEST_FILES)
> +
> + @for SUBDIR in $(SUBDIRS); do \
> + $(MAKE) -C $$SUBDIR INSTALL_PATH=$(INSTALL_PATH)/$$SUBDIR install; \
> + done;
> +endef
> +
> +override define EMIT_TESTS
> + echo "./run.sh"
> +endef
Ditto.
cheers
next prev parent reply other threads:[~2015-03-29 23:49 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 [this message]
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 ` [PATCH 4/5] selftest: Add futex tests to the top-level Makefile Darren Hart
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 2/5] selftest/futex: Update Makefile to use lib.mk 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=1427672978.4218.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=dave@stgolabs.net \
--cc=dvhart@linux.intel.com \
--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
Powered by JetHome