From: SeongJae Park <sj38.park@gmail.com>
To: shuah@kernel.org
Cc: bamvor.zhangjian@linaro.org, shorne@gmail.com,
davem@davemloft.net, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 3/3] selftest/net/Makefile: Specify output with $(OUTPUT)
Date: Sun, 18 Jun 2017 09:56:04 +0900 [thread overview]
Message-ID: <20170618005604.17639-4-sj38.park@gmail.com> (raw)
In-Reply-To: <20170618005604.17639-1-sj38.park@gmail.com>
After commit a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT"),
net selftest build fails because it points output file without $(OUTPUT)
yet. This commit fixes the error.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")
---
tools/testing/selftests/net/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/testing/selftests/net/Makefile b/tools/testing/selftests/net/Makefile
index 35cbb4cba410..f6c9dbf478f8 100644
--- a/tools/testing/selftests/net/Makefile
+++ b/tools/testing/selftests/net/Makefile
@@ -3,8 +3,6 @@
CFLAGS = -Wall -Wl,--no-as-needed -O2 -g
CFLAGS += -I../../../../usr/include/
-reuseport_bpf_numa: LDFLAGS += -lnuma
-
TEST_PROGS := run_netsocktests run_afpackettests test_bpf.sh netdevice.sh
TEST_GEN_FILES = socket
TEST_GEN_FILES += psock_fanout psock_tpacket
@@ -13,3 +11,4 @@ TEST_GEN_FILES += reuseport_dualstack
include ../lib.mk
+$(OUTPUT)/reuseport_bpf_numa: LDFLAGS += -lnuma
--
2.13.0
next prev parent reply other threads:[~2017-06-18 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 0:56 [PATCH 0/3] selftest: Fix build errors SeongJae Park
2017-06-18 0:56 ` [PATCH 1/3] selftest/memfd/Makefile: Fix build error SeongJae Park
2017-06-18 0:56 ` [PATCH 2/3] selftest/intel_pstate/aperf: Use LDLIBS instead of LDFLAGS SeongJae Park
2017-06-18 0:56 ` SeongJae Park [this message]
2017-06-18 2:48 ` [PATCH 3/3] selftest/net/Makefile: Specify output with $(OUTPUT) David Miller
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=20170618005604.17639-4-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shorne@gmail.com \
--cc=shuah@kernel.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).