From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: shuah@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
torvalds@linux-foundation.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH] selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set
Date: Fri, 10 May 2019 21:37:31 -0700 [thread overview]
Message-ID: <20190511043729.3o4enh35lrmne3kd@ast-mbp> (raw)
In-Reply-To: <20190511025249.32678-1-skhan@linuxfoundation.org>
On Fri, May 10, 2019 at 08:52:49PM -0600, Shuah Khan wrote:
> commit 8ce72dc32578 ("selftests: fix headers_install circular dependency")
> broke bpf build/test workflow. When KBUILD_OUTPUT is set, bpf objects end
> up in KBUILD_OUTPUT build directory instead of in ../selftests/bpf.
>
> The following bpf workflow breaks when it can't find the test_verifier:
>
> cd tools/testing/selftests/bpf; make; ./test_verifier;
>
> Fix it to set OUTPUT only when it is undefined in lib.mk. It didn't need
> to be set in the first place.
>
> Fixes: commit 8ce72dc32578 ("selftests: fix headers_install circular dependency")
>
> Reported-by: Alexei Starovoitov <alexei.starovoitov@gmail.com>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
'git am' couldn't apply this patch because "sha1 information is lacking",
but the patch itself looks good.
Acked-by: Alexei Starovoitov <ast@kernel.org>
Thanks for the quick fix.
next prev parent reply other threads:[~2019-05-11 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 2:52 [PATCH] selftests: fix bpf build/test workflow regression when KBUILD_OUTPUT is set Shuah Khan
2019-05-11 4:37 ` Alexei Starovoitov [this message]
2019-05-16 18:36 ` Alexei Starovoitov
2019-05-16 19:18 ` 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=20190511043729.3o4enh35lrmne3kd@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=torvalds@linux-foundation.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).