netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, shuah@kernel.org, sdf@google.com,
	donald.hunter@gmail.com, linux-kselftest@vger.kernel.org,
	petrm@nvidia.com
Subject: Re: [PATCH net-next v3 0/5] selftests: net: groundwork for YNL-based tests
Date: Mon, 08 Apr 2024 10:50:27 +0000	[thread overview]
Message-ID: <171257342732.21044.16185402025320251923.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405024526.2752998-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu,  4 Apr 2024 19:45:21 -0700 you wrote:
> Currently the options for writing networking tests are C, bash or
> some mix of the two. YAML/Netlink gives us the ability to easily
> interface with Netlink in higher level laguages. In particular,
> there is a Python library already available in tree, under tools/net.
> Add the scaffolding which allows writing tests using this library.
> 
> The "scaffolding" is needed because the library lives under
> tools/net and uses YAML files from under Documentation/.
> So we need a small amount of glue code to find those things
> and add them to TEST_FILES.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/5] selftests: net: add scaffolding for Netlink tests in Python
    https://git.kernel.org/netdev/net-next/c/b86761ff6374
  - [net-next,v3,2/5] selftests: nl_netdev: add a trivial Netlink netdev test
    https://git.kernel.org/netdev/net-next/c/796c8c7fd257
  - [net-next,v3,3/5] netdevsim: report stats by default, like a real device
    https://git.kernel.org/netdev/net-next/c/f216306bfb60
  - [net-next,v3,4/5] selftests: drivers: add scaffolding for Netlink tests in Python
    https://git.kernel.org/netdev/net-next/c/b4db9f840283
  - [net-next,v3,5/5] testing: net-drv: add a driver test for stats reporting
    https://git.kernel.org/netdev/net-next/c/f0e6c86e4bab

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



      parent reply	other threads:[~2024-04-08 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  2:45 [PATCH net-next v3 0/5] selftests: net: groundwork for YNL-based tests Jakub Kicinski
2024-04-05  2:45 ` [PATCH net-next v3 1/5] selftests: net: add scaffolding for Netlink tests in Python Jakub Kicinski
2024-04-05  2:45 ` [PATCH net-next v3 2/5] selftests: nl_netdev: add a trivial Netlink netdev test Jakub Kicinski
2024-04-05  2:45 ` [PATCH net-next v3 3/5] netdevsim: report stats by default, like a real device Jakub Kicinski
2024-04-05  2:45 ` [PATCH net-next v3 4/5] selftests: drivers: add scaffolding for Netlink tests in Python Jakub Kicinski
2024-04-05  2:45 ` [PATCH net-next v3 5/5] testing: net-drv: add a driver test for stats reporting Jakub Kicinski
2024-04-08 10:50 ` 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=171257342732.21044.16185402025320251923.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=sdf@google.com \
    --cc=shuah@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).