From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang@kernel.org>
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
jakub@cloudflare.com, tanggeliang@kylinos.cn,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] Free strdup memory in selftests
Date: Mon, 29 Apr 2024 23:20:30 +0000 [thread overview]
Message-ID: <171443283038.1398.7034964733309861371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1714374022.git.tanggeliang@kylinos.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 29 Apr 2024 15:07:32 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Two fixes to free strdup memory in selftests to avoid memory leaks.
>
> Geliang Tang (2):
> selftests/bpf: Free strdup memory in test_sockmap
> selftests/bpf: Free strdup memory in veristat
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] selftests/bpf: Free strdup memory in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/237c522c1d5d
- [bpf-next,2/2] selftests/bpf: Free strdup memory in veristat
https://git.kernel.org/bpf/bpf-next/c/25927d0a1bec
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:[~2024-04-29 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 7:07 [PATCH bpf-next 0/2] Free strdup memory in selftests Geliang Tang
2024-04-29 7:07 ` [PATCH bpf-next 1/2] selftests/bpf: Free strdup memory in test_sockmap Geliang Tang
2024-04-29 15:53 ` Yonghong Song
2024-04-29 19:56 ` John Fastabend
2024-04-29 7:07 ` [PATCH bpf-next 2/2] selftests/bpf: Free strdup memory in veristat Geliang Tang
2024-04-29 15:53 ` Yonghong Song
2024-04-29 19:57 ` John Fastabend
2024-04-29 23: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=171443283038.1398.7034964733309861371.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=geliang@kernel.org \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanggeliang@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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