From: Daniel Borkmann <daniel@iogearbox.net>
To: Quentin Monnet <quentin.monnet@netronome.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
oss-drivers@netronome.com,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: [PATCH bpf-next 0/2] selftests: bpftool: skip build tests if not in tree
Date: Thu, 21 Nov 2019 09:59:05 +0100 [thread overview]
Message-ID: <20191121085905.GD31576@pc-11.home> (raw)
In-Reply-To: <20191119105010.19189-1-quentin.monnet@netronome.com>
On Tue, Nov 19, 2019 at 10:50:08AM +0000, Quentin Monnet wrote:
> The build test script for bpftool attempts to detect the toplevel path of
> the kernel repository and attempts to build bpftool from there.
>
> If it fails to find the correct directory, or if bpftool files are missing
> for another reason (e.g. kselftests built on a first machine and copied
> onto another, without bpftool sources), then it is preferable to skip the
> tests entirely rather than dumping useless error messages.
>
> The first patch moves the EXIT trap in the script lower down in the code,
> to avoid tampering with return value on early exits at the beginning of the
> script; then the second patch makes sure that we skip the build tests if
> bpftool's Makefile is not found at its expected location.
>
> Jakub Kicinski (1):
> selftests: bpftool: skip the build test if not in tree
>
> Quentin Monnet (1):
> selftests: bpftool: set EXIT trap after usage function
>
> .../selftests/bpf/test_bpftool_build.sh | 30 +++++++++++--------
> 1 file changed, 17 insertions(+), 13 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2019-11-21 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 10:50 [PATCH bpf-next 0/2] selftests: bpftool: skip build tests if not in tree Quentin Monnet
2019-11-19 10:50 ` [PATCH bpf-next 1/2] selftests: bpftool: set EXIT trap after usage function Quentin Monnet
2019-11-19 10:50 ` [PATCH bpf-next 2/2] selftests: bpftool: skip the build test if not in tree Quentin Monnet
2019-11-21 8:59 ` Daniel Borkmann [this message]
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=20191121085905.GD31576@pc-11.home \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=quentin.monnet@netronome.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).