From: Daniel Borkmann <daniel@iogearbox.net>
To: Alan Maguire <alan.maguire@oracle.com>, ast@kernel.org, andriin@fb.com
Cc: kafai@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
shuah@kernel.org, sean@mess.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf 0/2] selftests/bpf: add missing CONFIG values to test config
Date: Sat, 23 May 2020 01:37:40 +0200 [thread overview]
Message-ID: <2f1368e0-c74e-2fd3-430c-4692243e3d63@iogearbox.net> (raw)
In-Reply-To: <1590147389-26482-1-git-send-email-alan.maguire@oracle.com>
On 5/22/20 1:36 PM, Alan Maguire wrote:
> Selftests "config" file is intended to represent the config required
> to run the tests; a few values are missing for the BPF selftests
> and these can result in test failures due to missing helpers etc.
> Add the missing values as they will help document the config needed
> for a clean BPF selftests run.
>
> Alan Maguire (2):
> selftests/bpf: CONFIG_IPV6_SEG6_BPF required for test_seg6_loop.o
> selftests/bpf: CONFIG_LIRC required for test_lirc_mode2.sh
>
> tools/testing/selftests/bpf/config | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied to bpf-next, thanks!
prev parent reply other threads:[~2020-05-22 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 11:36 [PATCH bpf 0/2] selftests/bpf: add missing CONFIG values to test config Alan Maguire
2020-05-22 11:36 ` [PATCH bpf 1/2] selftests/bpf: CONFIG_IPV6_SEG6_BPF required for test_seg6_loop.o Alan Maguire
2020-05-22 11:36 ` [PATCH bpf 2/2] selftests/bpf: CONFIG_LIRC required for test_lirc_mode2.sh Alan Maguire
2020-05-22 23:37 ` 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=2f1368e0-c74e-2fd3-430c-4692243e3d63@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alan.maguire@oracle.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean@mess.org \
--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).