From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
idosch@nvidia.com, mlxsw@nvidia.com, vmykhaliuk@nvidia.com,
amcohen@nvidia.com, jiri@nvidia.com
Subject: Re: [PATCH net-next] mlxsw: spectrum_flower: Do not allow mixing sample and mirror actions
Date: Thu, 12 Dec 2024 04:30:45 +0000 [thread overview]
Message-ID: <173397784500.1847197.12759000313918649518.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d6c979914e8706dbe1dedbaf29ffffb0b8d71166.1733822570.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Dec 2024 10:45:37 +0100 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The device does not support multiple mirror actions per rule and the
> driver rejects such configuration:
>
> # tc filter add dev swp1 ingress pref 1 proto ip flower skip_sw action mirred egress mirror dev swp2 action mirred egress mirror dev swp3
> Error: mlxsw_spectrum: Multiple mirror actions per rule are not supported.
> We have an error talking to the kernel
>
> [...]
Here is the summary with links:
- [net-next] mlxsw: spectrum_flower: Do not allow mixing sample and mirror actions
https://git.kernel.org/netdev/net-next/c/175dd9079ecb
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-12-12 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 9:45 [PATCH net-next] mlxsw: spectrum_flower: Do not allow mixing sample and mirror actions Petr Machata
2024-12-10 9:50 ` Michal Swiatkowski
2024-12-10 10:15 ` Kalesh Anakkur Purayil
2024-12-12 4: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=173397784500.1847197.12759000313918649518.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vmykhaliuk@nvidia.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;
as well as URLs for NNTP newsgroup(s).