From: patchwork-bot+netdevbpf@kernel.org
To: Phil Sutter <phil@nwl.cc>
Cc: pabeni@redhat.com, pablo@netfilter.org,
netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
fw@strlen.de, horms@kernel.org
Subject: Re: [net-next PATCH] selftests: netfilter: Fix skip of wildcard interface test
Date: Wed, 28 May 2025 07:53:14 +0000 [thread overview]
Message-ID: <174841879424.2284365.14495950610695273901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250527094117.18589-1-phil@nwl.cc>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 27 May 2025 11:41:17 +0200 you wrote:
> The script is supposed to skip wildcard interface testing if unsupported
> by the host's nft tool. The failing check caused script abort due to
> 'set -e' though. Fix this by running the potentially failing nft command
> inside the if-conditional pipe.
>
> Fixes: 73db1b5dab6f ("selftests: netfilter: Torture nftables netdev hooks")
> Signed-off-by: Phil Sutter <phil@nwl.cc>
>
> [...]
Here is the summary with links:
- [net-next] selftests: netfilter: Fix skip of wildcard interface test
https://git.kernel.org/netdev/net-next/c/6da5f1b4b4a0
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:[~2025-05-28 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 9:41 [net-next PATCH] selftests: netfilter: Fix skip of wildcard interface test Phil Sutter
2025-05-27 9:46 ` Pablo Neira Ayuso
2025-05-28 7:50 ` Paolo Abeni
2025-05-28 7:53 ` 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=174841879424.2284365.14495950610695273901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.