From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, tj@kernel.org, memxor@gmail.com,
martin.lau@kernel.org, linux-lists@etsalapatis.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v7 0/4] Task local data
Date: Sat, 02 Aug 2025 01:15:12 +0000 [thread overview]
Message-ID: <175409731275.4179816.2887052648677961170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250730185903.3574598-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 30 Jul 2025 11:58:51 -0700 you wrote:
> v6 -> v7
> - Fix typos and improve the clarity of the cover letter (Emil)
> - Some variable naming changes to make it less confusing (Emil)
> - Add retry in tld_obj_init() as bpf_task_storage_get_recur() with
> BPF_LOCAL_STORAGE_GET_F_CREATE can fail if the task local storage
> is also being modified by other threads on the same CPU. This can
> be especially easy to trigger in CI VM that only has two CPUs.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/4] bpf: Allow syscall bpf programs to call non-recur helpers
https://git.kernel.org/bpf/bpf-next/c/86de56487e5f
- [bpf-next,v7,2/4] selftests/bpf: Introduce task local data
https://git.kernel.org/bpf/bpf-next/c/31e838e1cdf4
- [bpf-next,v7,3/4] selftests/bpf: Test basic task local data operations
https://git.kernel.org/bpf/bpf-next/c/120f1a950e49
- [bpf-next,v7,4/4] selftests/bpf: Test concurrent task local data key creation
https://git.kernel.org/bpf/bpf-next/c/784181141782
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:[~2025-08-02 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 18:58 [PATCH bpf-next v7 0/4] Task local data Amery Hung
2025-07-30 18:58 ` [PATCH bpf-next v7 1/4] bpf: Allow syscall bpf programs to call non-recur helpers Amery Hung
2025-07-31 18:26 ` Emil Tsalapatis
2025-07-30 18:58 ` [PATCH bpf-next v7 2/4] selftests/bpf: Introduce task local data Amery Hung
2025-07-31 18:27 ` Emil Tsalapatis
2025-07-30 18:58 ` [PATCH bpf-next v7 3/4] selftests/bpf: Test basic task local data operations Amery Hung
2025-07-31 18:27 ` Emil Tsalapatis
2025-07-30 18:58 ` [PATCH bpf-next v7 4/4] selftests/bpf: Test concurrent task local data key creation Amery Hung
2025-07-31 18:27 ` Emil Tsalapatis
2025-08-02 1:15 ` 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=175409731275.4179816.2887052648677961170.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=linux-lists@etsalapatis.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@kernel.org \
/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.