BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, jakub@cloudflare.com,
	john.fastabend@gmail.com, kernel-team@fb.com,
	martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v7 0/5] bpf: Add bpf_link support for sk_msg and sk_skb progs
Date: Thu, 11 Apr 2024 03:00:29 +0000	[thread overview]
Message-ID: <171280442998.1698.2738854742023755836.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240410043522.3736912-1-yonghong.song@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  9 Apr 2024 21:35:22 -0700 you wrote:
> One of our internal services started to use sk_msg program and currently
> it used existing prog attach/detach2 as demonstrated in selftests.
> But attach/detach of all other bpf programs are based on bpf_link.
> Consistent attach/detach APIs for all programs will make things easy to
> undersand and less error prone. So this patch added bpf_link
> support for BPF_PROG_TYPE_SK_MSG. Based on comments from
> previous RFC patch, I added BPF_PROG_TYPE_SK_SKB support as well
> as both program types have similar treatment w.r.t. bpf_link
> handling.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,1/5] bpf: Add bpf_link support for sk_msg and sk_skb progs
    https://git.kernel.org/bpf/bpf-next/c/699c23f02c65
  - [bpf-next,v7,2/5] libbpf: Add bpf_link support for BPF_PROG_TYPE_SOCKMAP
    https://git.kernel.org/bpf/bpf-next/c/849989af61ad
  - [bpf-next,v7,3/5] bpftool: Add link dump support for BPF_LINK_TYPE_SOCKMAP
    https://git.kernel.org/bpf/bpf-next/c/1f3e2091d25b
  - [bpf-next,v7,4/5] selftests/bpf: Refactor out helper functions for a few tests
    https://git.kernel.org/bpf/bpf-next/c/a15d58b2bc82
  - [bpf-next,v7,5/5] selftests/bpf: Add some tests with new bpf_program__attach_sockmap() APIs
    https://git.kernel.org/bpf/bpf-next/c/8ba218e625f0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-04-11  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  4:35 [PATCH bpf-next v7 0/5] bpf: Add bpf_link support for sk_msg and sk_skb progs Yonghong Song
2024-04-10  4:35 ` [PATCH bpf-next v7 1/5] " Yonghong Song
2024-04-10  4:35 ` [PATCH bpf-next v7 2/5] libbpf: Add bpf_link support for BPF_PROG_TYPE_SOCKMAP Yonghong Song
2024-04-10  4:35 ` [PATCH bpf-next v7 3/5] bpftool: Add link dump support for BPF_LINK_TYPE_SOCKMAP Yonghong Song
2024-04-10  4:35 ` [PATCH bpf-next v7 4/5] selftests/bpf: Refactor out helper functions for a few tests Yonghong Song
2024-04-10  4:35 ` [PATCH bpf-next v7 5/5] selftests/bpf: Add some tests with new bpf_program__attach_sockmap() APIs Yonghong Song
2024-04-11  3: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=171280442998.1698.2738854742023755836.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=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@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