LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: gorcunov@openvz.org, akpm@linux-foundation.org,
	tranmanphong@gmail.com, mpe@ellerman.id.au
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: [PATCH 0/3] selftests: ptrace, kcmp, efivars build failure fixes
Date: Tue, 10 Mar 2015 16:00:56 -0600	[thread overview]
Message-ID: <cover.1426022048.git.shuahkh@osg.samsung.com> (raw)

ptrace, efivars, and kcmp Makefiles don't have explicit build rule.
As a result, build fails when make is run from top level Makefile
target kselftest. Without the explicit rule, make works only when
it is run in the current directory or from selftests directory.
Fxing the problems by adding an explicit build rule to fix the
problem.

Shuah Khan (3):
  selftests: ptrace build fails when invoked from kselftest target
  selftests: efivars build fails when invoked from kselftest target
  selftests: kcmp build fails when invoked from kselftest target

 tools/testing/selftests/efivarfs/Makefile | 2 ++
 tools/testing/selftests/kcmp/Makefile     | 5 +++--
 tools/testing/selftests/ptrace/Makefile   | 5 +++--
 3 files changed, 8 insertions(+), 4 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-03-10 22:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 22:00 Shuah Khan [this message]
2015-03-10 22:00 ` [PATCH 1/3] selftests: ptrace build fails when invoked from kselftest target Shuah Khan
2015-03-10 22:00 ` [PATCH 2/3] selftests: efivars " Shuah Khan
2015-03-10 22:00 ` [PATCH 3/3] selftests: kcmp " Shuah Khan
2015-03-10 22:09   ` Cyrill Gorcunov
2015-03-10 22:41     ` Shuah Khan
2015-03-10 22:45       ` Cyrill Gorcunov
2015-03-10 23:35 ` [PATCH 0/3] selftests: ptrace, kcmp, efivars build failure fixes Michael Ellerman
2015-03-10 23:37   ` Shuah Khan
2015-03-10 23:40     ` Shuah Khan

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=cover.1426022048.git.shuahkh@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=gorcunov@openvz.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=tranmanphong@gmail.com \
    --subject='Re: [PATCH 0/3] selftests: ptrace, kcmp, efivars build failure fixes' \
    /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

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).