From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yhs@fb.com
Subject: Re: [PATCH bpf-next 0/1] selftests/bpf: support custom per-test flags and multiple expected messages
Date: Wed, 01 Mar 2023 19:20:18 +0000 [thread overview]
Message-ID: <167769841836.22651.2010535238574748988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230301175417.3146070-1-eddyz87@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Mar 2023 19:54:16 +0200 you wrote:
> This patch allows to specify program flags and multiple verifier log
> messages for the test_loader kind of tests. For example:
>
> tools/testing/selftets/bpf/progs/foobar.c:
>
> SEC("tc")
> __success __log_level(7)
> __msg("first message")
> __msg("next message")
> __flag(BPF_F_ANY_ALIGNMENT)
> int buz(struct __sk_buff *skb)
> { ... }
>
> [...]
Here is the summary with links:
- [bpf-next,1/1] selftests/bpf: support custom per-test flags and multiple expected messages
https://git.kernel.org/bpf/bpf-next/c/35cbf7f91568
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-01 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 17:54 [PATCH bpf-next 0/1] selftests/bpf: support custom per-test flags and multiple expected messages Eduard Zingerman
2023-03-01 17:54 ` [PATCH bpf-next 1/1] " Eduard Zingerman
2023-03-01 19:20 ` patchwork-bot+netdevbpf [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=167769841836.22651.2010535238574748988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yhs@fb.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