netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, gavinl@nvidia.com, gavi@nvidia.com
Subject: Re: [net 1/7] net/mlx5e: Set uplink rep as NETNS_LOCAL
Date: Thu, 23 Mar 2023 06:00:19 +0000	[thread overview]
Message-ID: <167955121998.17973.16248642901272759046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230321211135.47711-2-saeed@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:

On Tue, 21 Mar 2023 14:11:29 -0700 you wrote:
> From: Gavin Li <gavinl@nvidia.com>
> 
> Previously, NETNS_LOCAL was not set for uplink representors, inconsistent
> with VF representors, and allowed the uplink representor to be moved
> between net namespaces and separated from the VF representors it shares
> the core device with. Such usage would break the isolation model of
> namespaces, as devices in different namespaces would have access to
> shared memory.
> 
> [...]

Here is the summary with links:
  - [net,1/7] net/mlx5e: Set uplink rep as NETNS_LOCAL
    https://git.kernel.org/netdev/net/c/c83172b0639c
  - [net,2/7] net/mlx5e: Block entering switchdev mode with ns inconsistency
    https://git.kernel.org/netdev/net/c/662404b24a4c
  - [net,3/7] net/mlx5: Fix steering rules cleanup
    https://git.kernel.org/netdev/net/c/922f56e9a795
  - [net,4/7] net/mlx5e: Initialize link speed to zero
    https://git.kernel.org/netdev/net/c/6e9d51b1a5cb
  - [net,5/7] net/mlx5e: Overcome slow response for first macsec ASO WQE
    https://git.kernel.org/netdev/net/c/7e3fce82d945
  - [net,6/7] net/mlx5: Read the TC mapping of all priorities on ETS query
    https://git.kernel.org/netdev/net/c/44d553188c38
  - [net,7/7] net/mlx5: E-Switch, Fix an Oops in error handling code
    https://git.kernel.org/netdev/net/c/640fcdbcf27f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-03-23  6:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 21:11 [pull request][net 0/7] mlx5 fixes 2023-03-21 Saeed Mahameed
2023-03-21 21:11 ` [net 1/7] net/mlx5e: Set uplink rep as NETNS_LOCAL Saeed Mahameed
2023-03-23  6:00   ` patchwork-bot+netdevbpf [this message]
2023-03-21 21:11 ` [net 2/7] net/mlx5e: Block entering switchdev mode with ns inconsistency Saeed Mahameed
2023-03-21 21:11 ` [net 3/7] net/mlx5: Fix steering rules cleanup Saeed Mahameed
2023-03-21 21:11 ` [net 4/7] net/mlx5e: Initialize link speed to zero Saeed Mahameed
2023-03-21 21:11 ` [net 5/7] net/mlx5e: Overcome slow response for first macsec ASO WQE Saeed Mahameed
2023-03-21 21:11 ` [net 6/7] net/mlx5: Read the TC mapping of all priorities on ETS query Saeed Mahameed
2023-03-21 21:11 ` [net 7/7] net/mlx5: E-Switch, Fix an Oops in error handling code Saeed Mahameed

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=167955121998.17973.16248642901272759046.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gavi@nvidia.com \
    --cc=gavinl@nvidia.com \
    --cc=kuba@kernel.org \
    --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 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).