All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Vineet Gupta <vineet.gupta@linux.dev>, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/3] selftests/bpf: name the remaining placeholder programs dummy_test [NFC]
Date: Mon, 24 Aug 2026 11:46:15 -0700	[thread overview]
Message-ID: <12fa2710ff8650bb8cd89b9ffc128b419f43a254.camel@gmail.com> (raw)
In-Reply-To: <20260821201316.1059129-2-vineet.gupta@linux.dev>

On Fri, 2026-08-21 at 13:13 -0700, Vineet Gupta wrote:
> Eleven of the thirteen feature-gated placeholder programs are called
> dummy_test. Two are not: hence this patch.
> 
> This is purely cosmetic as nothing depends on those names.
> The non-complaint setups use RUN_TESTS(skel) which does thru all
> programs normally. This is just more consistent and grep friendly.
> 
> Signed-off-by: Vineet Gupta <vineet.gupta@linux.dev>
> ---

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

  reply	other threads:[~2026-08-24 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 20:13 [PATCH bpf-next 0/3] selftests/bpf: unblock bpf-gcc test coverage Vineet Gupta
2026-08-21 20:13 ` [PATCH bpf-next 1/3] selftests/bpf: name the remaining placeholder programs dummy_test [NFC] Vineet Gupta
2026-08-24 18:46   ` Eduard Zingerman [this message]
2026-08-21 20:13 ` [PATCH bpf-next 2/3] selftests/bpf: report placeholder tests as SKIP, not OK Vineet Gupta
2026-08-21 21:00   ` bot+bpf-ci
2026-08-21 23:48     ` Vineet Gupta
2026-08-24 18:53   ` Eduard Zingerman
2026-08-21 20:13 ` [PATCH bpf-next 3/3] selftests/bpf: Enable some of the blocked cpuv4 instruction tests for bpf-gcc Vineet Gupta
2026-08-21 20:19   ` sashiko-bot
2026-08-21 23:38     ` Vineet Gupta
2026-08-24 19:04   ` Eduard Zingerman

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=12fa2710ff8650bb8cd89b9ffc128b419f43a254.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=vineet.gupta@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.