From: patchwork-bot+netdevbpf@kernel.org
To: Qiang Wang <wangqiang.wq.frank@bytedance.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
hengqi.chen@gmail.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
zhouchengming@bytedance.com, songmuchun@bytedance.com,
duanxiongchun@bytedance.com, shekairui@bytedance.com
Subject: Re: [PATCH v2 1/2] libbpf: Use probe_name for legacy kprobe
Date: Wed, 05 Jan 2022 23:40:08 +0000 [thread overview]
Message-ID: <164142600886.21166.4094526896575840947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211227130713.66933-1-wangqiang.wq.frank@bytedance.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 27 Dec 2021 21:07:12 +0800 you wrote:
> Fix a bug in commit 46ed5fc33db9, which wrongly used the
> func_name instead of probe_name to register legacy kprobe.
>
> Fixes: 46ed5fc33db9 ("libbpf: Refactor and simplify legacy kprobe code")
> Reviewed-by: Hengqi Chen <hengqi.chen@gmail.com>
> Tested-by: Hengqi Chen <hengqi.chen@gmail.com>
> Co-developed-by: Chengming Zhou <zhouchengming@bytedance.com>
> Signed-off-by: Qiang Wang <wangqiang.wq.frank@bytedance.com>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
>
> [...]
Here is the summary with links:
- [v2,1/2] libbpf: Use probe_name for legacy kprobe
https://git.kernel.org/bpf/bpf-next/c/71cff670baff
- [v2,2/2] libbpf: Support repeated legacy kprobes on same function
https://git.kernel.org/bpf/bpf-next/c/51a33c60f1c2
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-01-05 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 13:07 [PATCH v2 1/2] libbpf: Use probe_name for legacy kprobe Qiang Wang
2021-12-27 13:07 ` [PATCH v2 2/2] libbpf: Support repeated legacy kprobes on same function Qiang Wang
2022-01-05 23:40 ` 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=164142600886.21166.4094526896575840947.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=duanxiongchun@bytedance.com \
--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=netdev@vger.kernel.org \
--cc=shekairui@bytedance.com \
--cc=songliubraving@fb.com \
--cc=songmuchun@bytedance.com \
--cc=wangqiang.wq.frank@bytedance.com \
--cc=yhs@fb.com \
--cc=zhouchengming@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.