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, mptcp@lists.linux.dev
Subject: Re: [PATCH bpf v4 0/2] Two fixes for test_sockmap
Date: Thu, 11 Apr 2024 18:10:29 +0000 [thread overview]
Message-ID: <171285902939.2178.1171272108619447378.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1712639568.git.tanggeliang@kylinos.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Tue, 9 Apr 2024 13:18:38 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v4:
> - address Martin's comments for v3. (thanks.)
> - add Yonghong's "Acked-by" tags. (thanks.)
> - update subject-prefix from "bpf-next" to "bpf".
>
> [...]
Here is the summary with links:
- [bpf,v4,1/2] selftests/bpf: Add F_SETFL for fcntl in test_sockmap
(no matching commit)
- [bpf,v4,2/2] selftests/bpf: Fix umount cgroup2 error in test_sockmap
https://git.kernel.org/bpf/bpf-next/c/d75142dbeb2b
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-11 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 5:18 [PATCH bpf v4 0/2] Two fixes for test_sockmap Geliang Tang
2024-04-09 5:18 ` [PATCH bpf v4 1/2] selftests/bpf: Add F_SETFL for fcntl in test_sockmap Geliang Tang
2024-04-11 18:10 ` Martin KaFai Lau
2024-04-17 8:14 ` Geliang Tang
2024-04-18 0:28 ` Martin KaFai Lau
2024-04-23 10:28 ` Geliang Tang
2024-04-25 12:26 ` Jakub Sitnicki
2024-04-09 5:18 ` [PATCH bpf v4 2/2] selftests/bpf: Fix umount cgroup2 error " Geliang Tang
2024-04-11 18: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=171285902939.2178.1171272108619447378.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=martin.lau@linux.dev \
--cc=mptcp@lists.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