The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Hoyeon Lee <hoyeon.lee@suse.com>,
	ast@kernel.org, daniel@iogearbox.net,  bpf@vger.kernel.org
Cc: 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,
	 linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [bpf-next] selftests/bpf: refactor snprintf_btf test to use bpf_strncmp
Date: Wed, 05 Nov 2025 14:22:33 -0800	[thread overview]
Message-ID: <29784285224aed7ffa9a44434251c75c96c2c26b.camel@gmail.com> (raw)
In-Reply-To: <20251105201415.227144-1-hoyeon.lee@suse.com>

On Thu, 2025-11-06 at 05:14 +0900, Hoyeon Lee wrote:
> The netif_receive_skb BPF program used in snprintf_btf test still uses
> a custom __strncmp. This is unnecessary as the bpf_strncmp helper is
> available and provides the same functionality.
> 
> This commit refactors the test to use the bpf_strncmp helper, removing
> the redundant custom implementation.
> 
> Signed-off-by: Hoyeon Lee <hoyeon.lee@suse.com>
> ---

Acked-by: Eduard Zingerman <eddyz87@gmail.com>

[...]

  reply	other threads:[~2025-11-05 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 20:14 [bpf-next] selftests/bpf: refactor snprintf_btf test to use bpf_strncmp Hoyeon Lee
2025-11-05 22:22 ` Eduard Zingerman [this message]
2025-11-05 22:45 ` Alexei Starovoitov
2025-11-05 22:52   ` Eduard Zingerman
2025-11-05 23:33     ` Alexei Starovoitov
2025-11-05 23:37       ` Eduard Zingerman
2025-11-05 23:43         ` Alexei Starovoitov
2025-11-06  3:26           ` Hoyeon Lee

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=29784285224aed7ffa9a44434251c75c96c2c26b.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=hoyeon.lee@suse.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=sdf@fomichev.me \
    --cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox