From: tyler.baker@linaro.org (Tyler Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] selftests: fixes for installation and cross compilation
Date: Tue, 14 Apr 2015 15:50:56 -0700 [thread overview]
Message-ID: <1429051856-14557-1-git-send-email-tyler.baker@linaro.org> (raw)
This patch set fixes various issues observed when cross building and
installing selftests.
As I began investigating improving the test output format, I performed an
audit of the current tests to ensure all tests were able to execute on various
target architectures. I found that some tests did not install their binaries
and others required directories to be installed to execute properly. There
were also cases in which tests were being installed when they were never built.
With this series applied all tests compile when appropriate and install their
output properly.
I have tested this series by building, installing and deploying all selftests
to x86, arm and arm64 targets.
This series is based on next-20150414
Tyler Baker (7):
selftests: copy TEST_DIRS to INSTALL_PATH
selftests/ftrace: install test.d
selftests/breakpoints: emit skip and omit installation when tests are
not compiled
selftests/kdbus: install kdbus-test
selftests/x86: fix cross build logic
selftests/x86: install tests
selftests/exec: do not install subdir as it is already created
tools/testing/selftests/breakpoints/Makefile | 7 ++++-
tools/testing/selftests/exec/Makefile | 2 +-
tools/testing/selftests/ftrace/Makefile | 1 +
tools/testing/selftests/kdbus/Makefile | 2 ++
tools/testing/selftests/lib.mk | 3 ++
tools/testing/selftests/x86/Makefile | 41 +++++++++++++++++++++-------
6 files changed, 44 insertions(+), 12 deletions(-)
--
2.1.0
next reply other threads:[~2015-04-14 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 22:50 Tyler Baker [this message]
2015-04-16 4:08 ` [PATCH 0/7] selftests: fixes for installation and cross compilation Michael Ellerman
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=1429051856-14557-1-git-send-email-tyler.baker@linaro.org \
--to=tyler.baker@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).