From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: vmalik@redhat.com, ast@kernel.org, eddyz87@gmail.com,
rongtao@cestc.cn, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/2] Add kfuncs bpf_strcasestr and bpf_strncasestr
Date: Fri, 10 Oct 2025 17:10:18 +0000 [thread overview]
Message-ID: <176011621899.1050631.5241409064469976369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_98ABC9680EA2A20198904316DAE5A84AD906@qq.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 9 Oct 2025 09:20:14 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Add kfuncs bpf_strcasestr and bpf_strncasestr, which are extensions of
> bpf_strstr and bpf_strnstr, suitable for more scenarios.
>
> Rong Tao (2):
> bpf: add bpf_strcasestr,bpf_strncasestr kfuncs
> selftests/bpf: Test bpf_strcasestr,bpf_strncasestr kfuncs
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: add bpf_strcasestr,bpf_strncasestr kfuncs
https://git.kernel.org/bpf/bpf-next/c/b5b693f73589
- [bpf-next,v4,2/2] selftests/bpf: Test bpf_strcasestr,bpf_strncasestr kfuncs
https://git.kernel.org/bpf/bpf-next/c/eca0b643efc9
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-10-10 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 1:20 [PATCH bpf-next v4 0/2] Add kfuncs bpf_strcasestr and bpf_strncasestr Rong Tao
2025-10-10 17: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=176011621899.1050631.5241409064469976369.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
--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