[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <465892a7-a422-4380-b139-5fae25a5066a@qmon.net>
Date: Thu, 15 Jan 2026 11:33:01 +0000
From: Quentin Monnet <qmo@...n.net>
To: Alexis Lothoré (eBPF Foundation)
<alexis.lothore@...tlin.com>, Andrii Nakryiko <andrii@...nel.org>,
Eduard Zingerman <eddyz87@...il.com>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <martin.lau@...ux.dev>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>, Shuah Khan <shuah@...nel.org>
Cc: ebpf@...uxfoundation.org,
Bastien Curutchet <bastien.curutchet@...tlin.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH bpf-next 1/4] bpf/selftests: move assert macros into a
dedicated header
2026-01-14 09:59 UTC+0100 ~ "Alexis Lothoré (eBPF Foundation)"
<alexis.lothore@...tlin.com>
> The test_progs runner defines a large set of convenient assert macros to
> perform all the tests. Writing a new runner involves rewriting some
> macros if we want some basic testing features like standardized failure
> log.
>
> Export those assert macros from test_progs into a dedicated header so
> that we can use those in any test_runner. The sole requirement to be
> able to use those macros is to define a test__fail function in the
> runner that will be called whenever an assert fails.
>
> Signed-off-by: Alexis Lothoré (eBPF Foundation) <alexis.lothore@...tlin.com>
Acked-by: Quentin Monnet <qmo@...nel.org>
Powered by blists - more mailing lists