From: patchwork-bot+netdevbpf@kernel.org
To: Yuntao Wang <ytcoode@gmail.com>
Cc: skhan@linuxfoundation.org, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, hengqi.chen@gmail.com,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, shuah@kernel.org, songliubraving@fb.com,
yhs@fb.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Fix return value checks in perf_event_stackmap.c
Date: Fri, 08 Apr 2022 21:09:38 +0000 [thread overview]
Message-ID: <164945217886.693.13574650471014956022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220408041452.933944-1-ytcoode@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 8 Apr 2022 12:14:52 +0800 you wrote:
> The bpf_get_stackid() function may also return 0 on success.
>
> Correct checks from 'val > 0' to 'val >= 0' to ensure that they cover all
> possible success return values.
>
> Signed-off-by: Yuntao Wang <ytcoode@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Fix return value checks in perf_event_stackmap.c
https://git.kernel.org/bpf/bpf-next/c/658d87687cd5
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:[~2022-04-08 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:38 [PATCH bpf-next] selftests/bpf: Fix return value checks in perf_event_stackmap.c Yuntao Wang
2022-04-07 19:23 ` Shuah Khan
2022-04-08 4:14 ` [PATCH bpf-next v2] " Yuntao Wang
2022-04-08 21:09 ` 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=164945217886.693.13574650471014956022.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=hengqi.chen@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--cc=ytcoode@gmail.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;
as well as URLs for NNTP newsgroup(s).