From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
tariqt@nvidia.com, ayal@nvidia.com, moshe@nvidia.com,
roid@nvidia.com, saeedm@nvidia.com
Subject: Re: [net 1/3] net/mlx5: Fix setting of devlink traps in switchdev mode
Date: Thu, 15 Apr 2021 23:50:09 +0000 [thread overview]
Message-ID: <161853060920.30410.7488943298285569296.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210414231610.136376-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 14 Apr 2021 16:16:08 -0700 you wrote:
> From: Aya Levin <ayal@nvidia.com>
>
> Prevent setting of devlink traps on the uplink while in switchdev mode.
> In this mode, it is the SW switch responsibility to handle both packets
> with a mismatch in destination MAC or VLAN ID. Therefore, there are no
> flow steering tables to trap undesirable packets and driver crashes upon
> setting a trap.
>
> [...]
Here is the summary with links:
- [net,1/3] net/mlx5: Fix setting of devlink traps in switchdev mode
https://git.kernel.org/netdev/net/c/41bafb31dcd5
- [net,2/3] net/mlx5e: Fix setting of RS FEC mode
https://git.kernel.org/netdev/net/c/7a320c9db3e7
- [net,3/3] net/mlx5e: fix ingress_ifindex check in mlx5e_flower_parse_meta
https://git.kernel.org/netdev/net/c/e3e0f9b27970
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-04-15 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 23:16 [pull request][net 0/3] mlx5 fixes 2021-04-14 Saeed Mahameed
2021-04-14 23:16 ` [net 1/3] net/mlx5: Fix setting of devlink traps in switchdev mode Saeed Mahameed
2021-04-15 23:50 ` patchwork-bot+netdevbpf [this message]
2021-04-14 23:16 ` [net 2/3] net/mlx5e: Fix setting of RS FEC mode Saeed Mahameed
2021-04-14 23:16 ` [net 3/3] net/mlx5e: fix ingress_ifindex check in mlx5e_flower_parse_meta Saeed Mahameed
2021-04-14 23:31 ` [pull request][net 0/3] mlx5 fixes 2021-04-14 Jakub Kicinski
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=161853060920.30410.7488943298285569296.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ayal@nvidia.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 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.