From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, gal@nvidia.com, leonro@nvidia.com,
mbloch@nvidia.com
Subject: Re: [PATCH net-next V2] net/mlx5e: Allow set_rx_mode on uplink representor
Date: Sat, 21 Mar 2026 03:20:30 +0000 [thread overview]
Message-ID: <177406323053.2737822.485920694733400438.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260319005456.82745-1-saeed@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Mar 2026 17:54:56 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
>
> set_rx_mode handler was skipped on uplink representor, since uplink
> relies on FDB to forward all traffic to it by default, which works
> perfectly on a single PF per physical port configuration, as explicit
> mac request isn't required, but In case of multi-host and DPU
> environments, uplink can only use own mac address, as set_rx_mode
> wasn't honored in uplink rep.
>
> [...]
Here is the summary with links:
- [net-next,V2] net/mlx5e: Allow set_rx_mode on uplink representor
https://git.kernel.org/netdev/net-next/c/609e79253ace
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-03-21 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 0:54 [PATCH net-next V2] net/mlx5e: Allow set_rx_mode on uplink representor Saeed Mahameed
2026-03-21 3:20 ` 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=177406323053.2737822.485920694733400438.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.