From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: add more missing kernel config
Date: Fri, 09 Feb 2024 03:10:25 +0000 [thread overview]
Message-ID: <170744822598.23533.10537868285259056914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <38d3ca7f909736c1aef56e6244d67c82a9bba6ff.1707326987.git.pabeni@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Feb 2024 18:31:10 +0100 you wrote:
> The reuseport_addr_any.sh is currently skipping DCCP tests and
> pmtu.sh is skipping all the FOU/GUE related cases: add the missing
> options.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> Note that this does not include the - still missing - OVS-related
> option and pmtu.sh is will keep skipping such cases. Such tests
> will still fail in the virtme environment even with the relevant
> kernel options enabled, as they have an hard to solve dependency
> on systemd/dbus.
> The longer term plan is to move such test cases in the openvswitch
> directory. One short term option to avoid skips in selftests results
> while retaining the potential code coverage would be making the ovs
> tests disabled by default but reachable via pmtu.sh command line
> arguments.
>
> [...]
Here is the summary with links:
- [net] selftests: net: add more missing kernel config
https://git.kernel.org/netdev/net/c/02d9009f4e8c
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:[~2024-02-09 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:31 [PATCH net] selftests: net: add more missing kernel config Paolo Abeni
2024-02-07 18:04 ` Eric Dumazet
2024-02-09 3:10 ` 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=170744822598.23533.10537868285259056914.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).