public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net,  netdev@vger.kernel.org,
	 edumazet@google.com, pabeni@redhat.com,  andrew+netdev@lunn.ch,
	 horms@kernel.org, liuhangbin@gmail.com,  matttbe@kernel.org
Subject: Re: [PATCH net-next v2 00/10] tools: ynl: convert samples into selftests
Date: Sun, 08 Mar 2026 17:23:47 +0000	[thread overview]
Message-ID: <m28qc2grq4.fsf@gmail.com> (raw)
In-Reply-To: <20260307033630.1396085-1-kuba@kernel.org>

Jakub Kicinski <kuba@kernel.org> writes:

> The "samples" were always poor man's tests, used to manually
> confirm that C YNL works as expected. Since a proper tests/
> directory now exists move the samples and use the kselftest
> harness to turn them into selftests outputting KTAP.
>
> v2:
>  - add missing ASSERTs on allocation failures
>  - fix the exec in the bash wrappers preventing cleanup
> v1: https://lore.kernel.org/20260306020901.524105-1-kuba@kernel.org
>
> Jakub Kicinski (10):
>   tools: ynl: move samples to tests
>   tools: ynl: convert netdev sample to selftest
>   tools: ynl: convert ovs sample to selftest
>   tools: ynl: convert rt-link sample to selftest
>   tools: ynl: convert tc and tc-filter-add samples to selftest
>   tools: ynl: add netdevsim wrapper library for YNL tests
>   tools: ynl: convert devlink sample to selftest
>   tools: ynl: convert ethtool sample to selftest
>   tools: ynl: convert rt-addr sample to selftest
>   tools: ynl: convert rt-route sample to selftest

Series LGTM

Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
Tested-by: Donald Hunter <donald.hunter@gmail.com>

  parent reply	other threads:[~2026-03-08 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  3:36 [PATCH net-next v2 00/10] tools: ynl: convert samples into selftests Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 01/10] tools: ynl: move samples to tests Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 02/10] tools: ynl: convert netdev sample to selftest Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 03/10] tools: ynl: convert ovs " Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 04/10] tools: ynl: convert rt-link " Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 05/10] tools: ynl: convert tc and tc-filter-add samples " Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 06/10] tools: ynl: add netdevsim wrapper library for YNL tests Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 07/10] tools: ynl: convert devlink sample to selftest Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 08/10] tools: ynl: convert ethtool " Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 09/10] tools: ynl: convert rt-addr " Jakub Kicinski
2026-03-07  3:36 ` [PATCH net-next v2 10/10] tools: ynl: convert rt-route " Jakub Kicinski
2026-03-08 17:23 ` Donald Hunter [this message]
2026-03-10  0:10 ` [PATCH net-next v2 00/10] tools: ynl: convert samples into selftests patchwork-bot+netdevbpf

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=m28qc2grq4.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=matttbe@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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