BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
	yatsenko@meta.com
Subject: Re: [PATCH bpf-next v1] selftests/bpf: align kfuncs renamed in bpf tree
Date: Sat, 15 Nov 2025 02:01:47 +0000	[thread overview]
Message-ID: <176317210727.1905277.5246260123359446508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105132105.597344-1-mykyta.yatsenko5@gmail.com>

Hello:

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

On Wed,  5 Nov 2025 13:21:05 +0000 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
> 
> bpf_task_work_schedule_resume() and bpf_task_work_schedule_signal() have
> been renamed in bpf tree to bpf_task_work_schedule_resume_impl() and
> bpf_task_work_schedule_signal_impl() accordingly.
> There are few uses of these kfuncs in selftests that are not in bpf
> tree, so that when we port [1] into bpf-next, those BPF programs will
> not compile.
> This patch aligns those remaining callsites with the kfunc renaming.
> It should go on top of [1] when applying on bpf-next.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1] selftests/bpf: align kfuncs renamed in bpf tree
    https://git.kernel.org/bpf/bpf-next/c/a4d31f451d5b

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



      parent reply	other threads:[~2025-11-15  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 13:21 [PATCH bpf-next v1] selftests/bpf: align kfuncs renamed in bpf tree Mykyta Yatsenko
2025-11-05 13:57 ` bot+bpf-ci
2025-11-15  2:01 ` 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=176317210727.1905277.5246260123359446508.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=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.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