Linux Kernel Selftest development
 help / color / mirror / Atom feed
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, netdev@vger.kernel.org, idosch@nvidia.com,
	danieller@nvidia.com, amcohen@nvidia.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 00/16] selftests: Preparations for out-of-order-operations patches in mlxsw
Date: Wed, 21 Jun 2023 21:10:25 +0000	[thread overview]
Message-ID: <168738182597.695.7755172151141679906.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1687265905.git.petrm@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 20 Jun 2023 15:55:46 +0200 you wrote:
> The mlxsw driver currently makes the assumption that the user applies
> configuration in a bottom-up manner. Thus netdevices need to be added to
> the bridge before IP addresses are configured on that bridge or SVI added
> on top of it. Enslaving a netdevice to another netdevice that already has
> uppers is in fact forbidden by mlxsw for this reason. Despite this safety,
> it is rather easy to get into situations where the offloaded configuration
> is just plain wrong.
> 
> [...]

Here is the summary with links:
  - [net-next,01/16] selftests: forwarding: q_in_vni: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/8c3736ce595b
  - [net-next,02/16] selftests: forwarding: dual_vxlan_bridge: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/c801533304ca
  - [net-next,03/16] selftests: forwarding: skbedit_priority: Disable IPv6 autogen on a bridge
    https://git.kernel.org/netdev/net-next/c/d7442b7d288e
  - [net-next,04/16] selftests: forwarding: pedit_dsfield: Disable IPv6 autogen on a bridge
    https://git.kernel.org/netdev/net-next/c/f61018dc3e21
  - [net-next,05/16] selftests: forwarding: mirror_gre_*: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/92c3bb5393db
  - [net-next,06/16] selftests: forwarding: mirror_gre_*: Use port MAC for bridge address
    https://git.kernel.org/netdev/net-next/c/8fd32576e650
  - [net-next,07/16] selftests: forwarding: router_bridge: Use port MAC for bridge address
    https://git.kernel.org/netdev/net-next/c/5e71bf50c2e2
  - [net-next,08/16] selftests: mlxsw: q_in_q_veto: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/8cfdd300a5e9
  - [net-next,09/16] selftests: mlxsw: extack: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/a758dc469a9c
  - [net-next,10/16] selftests: mlxsw: mirror_gre_scale: Disable IPv6 autogen on a bridge
    https://git.kernel.org/netdev/net-next/c/32b3a7bf8570
  - [net-next,11/16] selftests: mlxsw: qos_dscp_bridge: Disable IPv6 autogen on a bridge
    https://git.kernel.org/netdev/net-next/c/6349f9bbbfb2
  - [net-next,12/16] selftests: mlxsw: qos_ets_strict: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/ec7023e6745e
  - [net-next,13/16] selftests: mlxsw: qos_mc_aware: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/ea2d5f757e91
  - [net-next,14/16] selftests: mlxsw: spectrum: q_in_vni_veto: Disable IPv6 autogen on a bridge
    https://git.kernel.org/netdev/net-next/c/08035d8e354d
  - [net-next,15/16] selftests: mlxsw: vxlan: Disable IPv6 autogen on bridges
    https://git.kernel.org/netdev/net-next/c/5541577521cc
  - [net-next,16/16] selftests: mlxsw: one_armed_router: Use port MAC for bridge address
    https://git.kernel.org/netdev/net-next/c/664bc72dd200

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



      parent reply	other threads:[~2023-06-21 21:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 13:55 [PATCH net-next 00/16] selftests: Preparations for out-of-order-operations patches in mlxsw Petr Machata
2023-06-20 13:55 ` [PATCH net-next 01/16] selftests: forwarding: q_in_vni: Disable IPv6 autogen on bridges Petr Machata
2023-06-20 13:55 ` [PATCH net-next 02/16] selftests: forwarding: dual_vxlan_bridge: " Petr Machata
2023-06-20 13:55 ` [PATCH net-next 03/16] selftests: forwarding: skbedit_priority: Disable IPv6 autogen on a bridge Petr Machata
2023-06-20 13:55 ` [PATCH net-next 04/16] selftests: forwarding: pedit_dsfield: " Petr Machata
2023-06-20 13:55 ` [PATCH net-next 05/16] selftests: forwarding: mirror_gre_*: Disable IPv6 autogen on bridges Petr Machata
2023-06-20 13:55 ` [PATCH net-next 06/16] selftests: forwarding: mirror_gre_*: Use port MAC for bridge address Petr Machata
2023-06-20 13:55 ` [PATCH net-next 07/16] selftests: forwarding: router_bridge: " Petr Machata
2023-06-20 13:55 ` [PATCH net-next 08/16] selftests: mlxsw: q_in_q_veto: Disable IPv6 autogen on bridges Petr Machata
2023-06-20 13:55 ` [PATCH net-next 09/16] selftests: mlxsw: extack: " Petr Machata
2023-06-20 13:55 ` [PATCH net-next 10/16] selftests: mlxsw: mirror_gre_scale: Disable IPv6 autogen on a bridge Petr Machata
2023-06-20 13:55 ` [PATCH net-next 11/16] selftests: mlxsw: qos_dscp_bridge: " Petr Machata
2023-06-20 13:55 ` [PATCH net-next 12/16] selftests: mlxsw: qos_ets_strict: Disable IPv6 autogen on bridges Petr Machata
2023-06-20 13:55 ` [PATCH net-next 13/16] selftests: mlxsw: qos_mc_aware: " Petr Machata
2023-06-20 13:56 ` [PATCH net-next 14/16] selftests: mlxsw: spectrum: q_in_vni_veto: Disable IPv6 autogen on a bridge Petr Machata
2023-06-20 13:56 ` [PATCH net-next 15/16] selftests: mlxsw: vxlan: Disable IPv6 autogen on bridges Petr Machata
2023-06-20 13:56 ` [PATCH net-next 16/16] selftests: mlxsw: one_armed_router: Use port MAC for bridge address Petr Machata
2023-06-21 21:10 ` 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=168738182597.695.7755172151141679906.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amcohen@nvidia.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=shuah@kernel.org \
    /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