From: patchwork-bot+netdevbpf@kernel.org
To: Marcelo Mendes Spessoto Junior <marcelomspessoto@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] net: selftests: adjustments to ipv6_flowlabel_mgr
Date: Wed, 12 Aug 2026 01:30:31 +0000 [thread overview]
Message-ID: <178649823188.1227528.4185778051969675653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807220942.421382-1-marcelomspessoto@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Aug 2026 19:09:37 -0300 you wrote:
> The ipv6_flowlabel_mgr test file was lacking coverage for the
> IPV6_FL_A_RENEW action, and the IPV6_FL_F_REMOTE and IPV6_FL_F_REFLECT
> flags. The first two patches from this set aim to add a proper test
> case for RENEW and REMOTE.
>
> The third patch was added to insert network namespace creation inside
> the test suite, instead of relying on external wrapper scripts. This
> change conforms to other net test implementations, such as
> tools/testing/selftests/net/icmp_rfc4884.c, and it is important for
> the fourth and fifth patches.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] selftests: net: test IPV6_FL_A_RENEW
https://git.kernel.org/netdev/net-next/c/bfad9937de98
- [net-next,v3,2/5] selftests: net: test IPV6_FL_F_REMOTE
https://git.kernel.org/netdev/net-next/c/39dd045c1514
- [net-next,v3,3/5] selftests: net: create own netns in ipv6_flowlabel_mgr
https://git.kernel.org/netdev/net-next/c/03df0d155ba1
- [net-next,v3,4/5] selftests: net: test IPV6_FL_F_REFLECT
https://git.kernel.org/netdev/net-next/c/b2690523a71f
- [net-next,v3,5/5] selftests: net: adopt harness for flow label mgr
https://git.kernel.org/netdev/net-next/c/b5d24f604506
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-08-12 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 22:09 [PATCH net-next v3 0/5] net: selftests: adjustments to ipv6_flowlabel_mgr Marcelo Mendes Spessoto Junior
2026-08-07 22:09 ` [PATCH net-next v3 1/5] selftests: net: test IPV6_FL_A_RENEW Marcelo Mendes Spessoto Junior
2026-08-07 22:09 ` [PATCH net-next v3 2/5] selftests: net: test IPV6_FL_F_REMOTE Marcelo Mendes Spessoto Junior
2026-08-07 22:09 ` [PATCH net-next v3 3/5] selftests: net: create own netns in ipv6_flowlabel_mgr Marcelo Mendes Spessoto Junior
2026-08-12 1:24 ` Jakub Kicinski
2026-08-07 22:09 ` [PATCH net-next v3 4/5] selftests: net: test IPV6_FL_F_REFLECT Marcelo Mendes Spessoto Junior
2026-08-07 22:09 ` [PATCH net-next v3 5/5] selftests: net: adopt harness for flow label mgr Marcelo Mendes Spessoto Junior
2026-08-12 1:30 ` 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=178649823188.1227528.4185778051969675653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=marcelomspessoto@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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