From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, puranjay12@gmail.com
Subject: Re: [PATCH bpf-next v5 0/2] Implement mechanism to signal other threads
Date: Mon, 21 Oct 2024 22:10:31 +0000 [thread overview]
Message-ID: <172954863101.459649.18336368288073439741.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241016084136.10305-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 16 Oct 2024 08:41:34 +0000 you wrote:
> This set implements a kfunc called bpf_send_signal_task() that is similar
> to sigqueue() as it can send a signal along with a cookie to a thread or
> thread group.
>
> The send_signal selftest has been updated to also test this new kfunc under
> all contexts.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] bpf: implement bpf_send_signal_task() kfunc
https://git.kernel.org/bpf/bpf-next/c/6280cf718db0
- [bpf-next,v5,2/2] selftests/bpf: Augment send_signal test with remote signaling
https://git.kernel.org/bpf/bpf-next/c/0e14189459f6
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-10-21 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:41 [PATCH bpf-next v5 0/2] Implement mechanism to signal other threads Puranjay Mohan
2024-10-16 8:41 ` [PATCH bpf-next v5 1/2] bpf: implement bpf_send_signal_task() kfunc Puranjay Mohan
2024-10-16 8:41 ` [PATCH bpf-next v5 2/2] selftests/bpf: Augment send_signal test with remote signaling Puranjay Mohan
2024-10-21 22: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=172954863101.459649.18336368288073439741.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=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
--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 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.