From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
Cc: davem@davemloft.net, andrew+netdev@lunn.ch, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
willemb@google.com, petrm@nvidia.com, dw@davidwei.uk,
carges@cloudflare.com, cjubran@nvidia.com, daskald@meta.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Add selftests for ntuple (NFC) rules
Date: Fri, 10 Apr 2026 22:40:35 +0000 [thread overview]
Message-ID: <177586083553.2670415.5524532409783816468.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260407164954.2977820-1-dimitri.daskalakis1@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Apr 2026 09:49:52 -0700 you wrote:
> From: Dimitri Daskalakis <daskald@meta.com>
>
> Thoroughly testing a device's NFC implementation can be tedious. The more
> features a device supports, the more combinations to validate.
>
> This series aims to ease that burden, validating the most common NFC rule
> combinations.
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: drv-net: Add ntuple (NFC) flow steering test
https://git.kernel.org/netdev/net-next/c/18589df9344c
- [net-next,2/2] selftests: drv-net: ntuple: Add dst-ip, src-port, dst-port fields
https://git.kernel.org/netdev/net-next/c/a66374a3eb02
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:[~2026-04-10 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 16:49 [PATCH net-next 0/2] Add selftests for ntuple (NFC) rules Dimitri Daskalakis
2026-04-07 16:49 ` [PATCH net-next 1/2] selftests: drv-net: Add ntuple (NFC) flow steering test Dimitri Daskalakis
2026-04-09 15:50 ` Jakub Kicinski
2026-04-09 20:28 ` Dimitri Daskalakis
2026-04-07 16:49 ` [PATCH net-next 2/2] selftests: drv-net: ntuple: Add dst-ip, src-port, dst-port fields Dimitri Daskalakis
2026-04-10 22:40 ` 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=177586083553.2670415.5524532409783816468.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=carges@cloudflare.com \
--cc=cjubran@nvidia.com \
--cc=daskald@meta.com \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=dw@davidwei.uk \
--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=shuah@kernel.org \
--cc=willemb@google.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