From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 0/2] bpf: Fix fill_link_info and add selftest
Date: Wed, 16 Aug 2023 14:50:21 +0000 [thread overview]
Message-ID: <169219742167.13455.2580251797431652897.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230813141900.1268-1-laoar.shao@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 13 Aug 2023 14:18:58 +0000 you wrote:
> Patch #1: Fix an error in fill_link_info reported by Dan
> Patch #2: Add selftest for #1
>
> v5->v6:
> - Fix BPF CI failure on aarch64
>
> v4->v5:
> - Comments from Yonghong
> - Replace 'offset' with '0'
> - Set err=-1 for default case
> - Only check return value of verify_kmulti_link_info
> - Comments from Jiri
> - Avoid retprobe argument
> - Use bpf_fentry_test* instead
> - Rename verify_kmulti_user_buffer
> - Define some variables as global value to simplify the code
>
> [...]
Here is the summary with links:
- [v6,bpf-next,1/2] bpf: Fix uninitialized symbol in bpf_perf_link_fill_kprobe()
https://git.kernel.org/bpf/bpf-next/c/0aa35162d2a1
- [v6,bpf-next,2/2] selftests/bpf: Add selftest for fill_link_info
https://git.kernel.org/bpf/bpf-next/c/23cf7aa539dc
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:[~2023-08-16 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 14:18 [PATCH v6 bpf-next 0/2] bpf: Fix fill_link_info and add selftest Yafang Shao
2023-08-13 14:18 ` [PATCH v6 bpf-next 1/2] bpf: Fix uninitialized symbol in bpf_perf_link_fill_kprobe() Yafang Shao
2023-08-13 14:19 ` [PATCH v6 bpf-next 2/2] selftests/bpf: Add selftest for fill_link_info Yafang Shao
2023-08-16 14:50 ` 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=169219742167.13455.2580251797431652897.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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