From: patchwork-bot+netdevbpf@kernel.org
To: Wang Yufen <wangyufen@huawei.com>
Cc: quentin@isovalent.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [bpf-next v9 0/3] bpftool: Add autoattach for bpf prog load|loadall
Date: Fri, 21 Oct 2022 16:10:18 +0000 [thread overview]
Message-ID: <166636861803.30010.17887941246508343977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1665736275-28143-1-git-send-email-wangyufen@huawei.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 14 Oct 2022 16:31:12 +0800 you wrote:
> This patchset add "autoattach" optional for "bpftool prog load(_all)" to support
> one-step load-attach-pin_link.
>
> v8 -> v9: fix link leak, and change pathname_concat(specify not just buffer
> pointer, but also it's size)
> v7 -> v8: for the programs not supporting autoattach, fall back to reguler pinning
> instead of skipping
> v6 -> v7: add info msg print and update doc for the skip program
> v5 -> v6: skip the programs not supporting auto-attach,
> and change optional name from "auto_attach" to "autoattach"
> v4 -> v5: some formatting nits of doc
> v3 -> v4: rename functions, update doc, bash and do_help()
> v2 -> v3: switch to extend prog load command instead of extend perf
> v2: https://patchwork.kernel.org/project/netdevbpf/patch/20220824033837.458197-1-weiyongjun1@huawei.com/
> v1: https://patchwork.kernel.org/project/netdevbpf/patch/20220816151725.153343-1-weiyongjun1@huawei.com/
>
> [...]
Here is the summary with links:
- [bpf-next,v9,1/3] bpftool: Add autoattach for bpf prog load|loadall
https://git.kernel.org/bpf/bpf-next/c/19526e701ea0
- [bpf-next,v9,2/3] bpftool: Update doc (add autoattach to prog load)
https://git.kernel.org/bpf/bpf-next/c/ff0e9a579ec9
- [bpf-next,v9,3/3] bpftool: Update the bash completion(add autoattach to prog load)
https://git.kernel.org/bpf/bpf-next/c/b81a67740075
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-10-21 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 8:31 [bpf-next v9 0/3] bpftool: Add autoattach for bpf prog load|loadall Wang Yufen
2022-10-14 8:31 ` [bpf-next v9 1/3] " Wang Yufen
2022-10-14 8:31 ` [bpf-next v9 2/3] bpftool: Update doc (add autoattach to prog load) Wang Yufen
2022-10-14 8:31 ` [bpf-next v9 3/3] bpftool: Update the bash completion(add " Wang Yufen
2022-10-21 16: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=166636861803.30010.17887941246508343977.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=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=trix@redhat.com \
--cc=wangyufen@huawei.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox