tools/testing/selftests/bpf/prog_tests/kfunc_call.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
There is a spelling mistake in an ASSERT_OK literal string. Fix it.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
V2: change subject line as per Mykola Lysenko's recommendation
---
tools/testing/selftests/bpf/prog_tests/kfunc_call.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/kfunc_call.c b/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
index 351fafa006fb..eede7c304f86 100644
--- a/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
+++ b/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
@@ -109,7 +109,7 @@ static void test_destructive(void)
{
__u64 save_caps = 0;
- ASSERT_OK(test_destructive_open_and_load(), "succesful_load");
+ ASSERT_OK(test_destructive_open_and_load(), "successful_load");
if (!ASSERT_OK(cap_disable_effective(1ULL << CAP_SYS_BOOT, &save_caps), "drop_caps"))
return;
--
2.37.1
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 17 Aug 2022 22:32:42 +0100 you wrote:
> There is a spelling mistake in an ASSERT_OK literal string. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> V2: change subject line as per Mykola Lysenko's recommendation
> ---
> tools/testing/selftests/bpf/prog_tests/kfunc_call.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [V2,next] selftests/bpf: Fix spelling mistake "succesful" (kfunc_call.c)
https://git.kernel.org/bpf/bpf-next/c/e918cd231ee6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Acked-by: Mykola Lysenko <mykolal@fb.com>
> On Aug 17, 2022, at 2:32 PM, Colin Ian King <colin.i.king@gmail.com> wrote:
>
> !-------------------------------------------------------------------|
> This Message Is From an External Sender
>
> |-------------------------------------------------------------------!
>
> There is a spelling mistake in an ASSERT_OK literal string. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> V2: change subject line as per Mykola Lysenko's recommendation
> ---
> tools/testing/selftests/bpf/prog_tests/kfunc_call.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/kfunc_call.c b/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
> index 351fafa006fb..eede7c304f86 100644
> --- a/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
> +++ b/tools/testing/selftests/bpf/prog_tests/kfunc_call.c
> @@ -109,7 +109,7 @@ static void test_destructive(void)
> {
> __u64 save_caps = 0;
>
> - ASSERT_OK(test_destructive_open_and_load(), "succesful_load");
> + ASSERT_OK(test_destructive_open_and_load(), "successful_load");
>
> if (!ASSERT_OK(cap_disable_effective(1ULL << CAP_SYS_BOOT, &save_caps), "drop_caps"))
> return;
> --
> 2.37.1
>
© 2016 - 2026 Red Hat, Inc.