From: patchwork-bot+netdevbpf@kernel.org
To: Alexey Gladkov <legion@kernel.org>
Cc: linux-kernel@vger.kernel.org, ast@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
andrii@kernel.org, daniel@iogearbox.net,
roberto.sassu@huawei.com, sdf@google.com
Subject: Re: [RESEND PATCH v1] selftests/bpf: Do not use sign-file as testcase
Date: Wed, 17 May 2023 14:10:19 +0000 [thread overview]
Message-ID: <168433261956.10644.15438316748787796174.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <88e3ab23029d726a2703adcf6af8356f7a2d3483.1684316821.git.legion@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 17 May 2023 11:49:46 +0200 you wrote:
> The sign-file utility (from scripts/) is used in prog_tests/verify_pkcs7_sig.c,
> but the utility should not be called as a test. Executing this utility
> produces the following error:
>
> selftests: /linux/tools/testing/selftests/bpf: urandom_read
> ok 16 selftests: /linux/tools/testing/selftests/bpf: urandom_read
>
> [...]
Here is the summary with links:
- [RESEND,v1] selftests/bpf: Do not use sign-file as testcase
https://git.kernel.org/bpf/bpf-next/c/f04a32b2c5b5
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-05-17 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:59 [PATCH v1] selftests/bpf: Do not use sign-file as testcase Alexey Gladkov
2023-04-27 18:28 ` Stanislav Fomichev
2023-04-27 20:38 ` Daniel Borkmann
2023-04-28 9:47 ` Alexey Gladkov
2023-04-28 7:14 ` Roberto Sassu
2023-05-17 9:49 ` [RESEND PATCH " Alexey Gladkov
2023-05-17 14:10 ` 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=168433261956.10644.15438316748787796174.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=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=sdf@google.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