From: Shuah Khan <shuahkh@osg.samsung.com>
To: gorcunov@openvz.org, tranmanphong@gmail.com, mpe@ellerman.id.au,
akpm@linux-foundation.org
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] selftests: Fix kcmp build to not require headers install
Date: Fri, 13 Mar 2015 19:45:04 -0600 [thread overview]
Message-ID: <1426297504-14432-2-git-send-email-shuahkh@osg.samsung.com> (raw)
In-Reply-To: <1426297504-14432-1-git-send-email-shuahkh@osg.samsung.com>
Change CFLAGS to look in uapi to allow kcmp to be built without
requiring headers install. This will make it easier to run tests
without going through the headers install step.
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
---
tools/testing/selftests/kcmp/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kcmp/Makefile b/tools/testing/selftests/kcmp/Makefile
index ff0eefd..d405ad4 100644
--- a/tools/testing/selftests/kcmp/Makefile
+++ b/tools/testing/selftests/kcmp/Makefile
@@ -1,5 +1,5 @@
CC := $(CROSS_COMPILE)$(CC)
-CFLAGS += -I../../../../usr/include/
+CFLAGS += -I../../../../include/uapi -I../../../../usr/include/
all: kcmp_test
--
2.1.0
next prev parent reply other threads:[~2015-03-14 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 1:45 [PATCH] selftests: Fix build failures when invoked from kselftest target Shuah Khan
2015-03-14 1:45 ` Shuah Khan [this message]
2015-03-16 11:00 ` [PATCH] selftests: Fix kcmp build to not require headers install Michael Ellerman
2015-03-18 15:04 ` Shuah Khan
2015-03-19 0:02 ` Michael Ellerman
2015-03-19 0:18 ` Shuah Khan
2015-03-19 0:51 ` Michael Ellerman
2015-03-16 0:38 ` [PATCH] selftests: Fix build failures when invoked from kselftest target Michael Ellerman
2015-03-18 16:46 ` 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=1426297504-14432-2-git-send-email-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 \
/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).