From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
martin.lau@linux.dev, rongtao@cestc.cn, sdf@fomichev.me,
song@kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next] samples/bpf: Remove sample tracex2
Date: Wed, 04 Sep 2024 19:00:35 +0000 [thread overview]
Message-ID: <172547643549.1133672.7645467399313819714.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_30ADAC88CB2915CA57E9512D4460035BA107@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 31 Aug 2024 08:03:38 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> In commit ba8de796baf4 ("net: introduce sk_skb_reason_drop function")
> kfree_skb_reason() becomes an inline function and cannot be traced.
>
> samples/bpf is abandonware by now, and we should slowly but surely
> convert whatever makes sense into BPF selftests under
> tools/testing/selftests/bpf and just get rid of the rest.
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: Remove sample tracex2
https://git.kernel.org/bpf/bpf-next/c/46f4ea04e053
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-09-04 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 1:18 [PATCH bpf-next] samples/bpf: tracex2: Replace kfree_skb from kprobe to tracepoint Rong Tao
2024-08-30 20:01 ` Andrii Nakryiko
2024-08-31 0:03 ` [PATCH bpf-next] samples/bpf: Remove sample tracex2 Rong Tao
2024-09-04 19:00 ` 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=172547643549.1133672.7645467399313819714.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@fomichev.me \
--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