linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tyler.baker@linaro.org (tyler.baker at linaro.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] selftests: installation fixes
Date: Tue, 12 May 2015 14:59:05 -0700	[thread overview]
Message-ID: <1431467947-29847-1-git-send-email-tyler.baker@linaro.org> (raw)

From: Tyler Baker <tyler.baker@linaro.org>

This is a follow up series to address a simple lib.mk installation issue[1]. 
Essentially, install is being called without checking that there exists test 
artifacts to install, which in turn causes 'make install' to fail. By creating 
a simple loop we can avoid if/elif/else blocks to determine if install actually 
needs to be called.

I've tested this series by building and deploying tests on x86[2], arm64[3], and arm[4] 
platforms.

This series is based on next-20150512.

[1] https://lkml.org/lkml/2015/4/20/746
[2] http://lava.kernelci.org/scheduler/job/83448/log_file#L_40
[3] http://lava.kernelci.org/scheduler/job/83665/log_file#L_44  
[4] http://lava.kernelci.org/scheduler/job/83442/log_file#L_65

Tyler Baker (2):
  selftests/lib.mk: fix INSTALL_RULE
  selftests/breakpoints: only set TEST_PROGS when built

 tools/testing/selftests/breakpoints/Makefile | 3 +--
 tools/testing/selftests/lib.mk               | 6 ++++--
 2 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-05-12 21:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 21:59 tyler.baker at linaro.org [this message]
2015-05-12 21:59 ` [PATCH 1/2] selftests/lib.mk: fix INSTALL_RULE tyler.baker at linaro.org
2015-05-12 22:02   ` Shuah Khan
2015-05-12 22:04     ` Tyler Baker
2015-05-12 22:07       ` Shuah Khan
2015-05-12 22:41         ` Tyler Baker
2015-05-12 21:59 ` [PATCH 2/2] selftests/breakpoints: only set TEST_PROGS when built tyler.baker at linaro.org
2015-05-13 21:41   ` Shuah Khan
2015-05-14 14:15     ` Tyler Baker
2015-05-14 15:27       ` Shuah Khan
2015-05-14 17:11         ` Tyler Baker

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=1431467947-29847-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).