From: patchwork-bot+netdevbpf@kernel.org
To: Yuran Pereira <yuran.pereira@hotmail.com>
Cc: haoluo@google.com, brauner@kernel.org,
linux-kselftest@vger.kernel.org, iii@linux.ibm.com,
daniel@iogearbox.net, linux-kernel@vger.kernel.org,
sinquersw@gmail.com, john.fastabend@gmail.com, ast@kernel.org,
kpsingh@kernel.org, song@kernel.org, sdf@google.com,
yonghong.song@linux.dev, mykolal@fb.com, bpf@vger.kernel.org,
shuah@kernel.org, jolsa@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org, kuifeng@meta.com
Subject: Re: [PATCH bpf-next v3 1/2] selftests/bpf: Convert CHECK macros to ASSERT_* macros in bpf_iter
Date: Thu, 02 Nov 2023 06:00:25 +0000 [thread overview]
Message-ID: <169890482549.9002.3230353368904918414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <DB3PR10MB6835E9C8DFCA226DD6FEF914E8A3A@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 28 Oct 2023 10:54:13 +0530 you wrote:
> As it was pointed out by Yonghong Song [1], in the bpf selftests the use
> of the ASSERT_* series of macros is preferred over the CHECK macro.
> This patch replaces all CHECK calls in bpf_iter with the appropriate
> ASSERT_* macros.
>
> [1] https://lore.kernel.org/lkml/0a142924-633c-44e6-9a92-2dc019656bf2@linux.dev
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] selftests/bpf: Convert CHECK macros to ASSERT_* macros in bpf_iter
https://git.kernel.org/bpf/bpf-next/c/ed47cb27586d
- [bpf-next,v3,2/2] selftests/bpf: Add malloc failure checks in bpf_iter
https://git.kernel.org/bpf/bpf-next/c/cb3c6a58be50
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2023-11-02 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1698461732.git.yuran.pereira@hotmail.com>
2023-10-28 5:24 ` [PATCH bpf-next v3 0/2] selftests/bpf: Replaces CHECK macros and adds malloc failure checks to bpf_iter Yuran Pereira
2023-10-28 5:24 ` [PATCH bpf-next v3 1/2] selftests/bpf: Convert CHECK macros to ASSERT_* macros in bpf_iter Yuran Pereira
2023-10-29 17:06 ` Yonghong Song
2023-10-30 19:39 ` Kui-Feng Lee
2023-11-02 6:00 ` patchwork-bot+netdevbpf [this message]
2023-10-28 5:24 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add malloc failure checks " Yuran Pereira
2023-10-29 17:07 ` Yonghong Song
2023-10-30 19:39 ` Kui-Feng Lee
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=169890482549.9002.3230353368904918414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuifeng@meta.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=sinquersw@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=yuran.pereira@hotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).