public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Petr Machata <petrm@nvidia•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
	mlxsw@nvidia•com, idosch@nvidia•com, danieller@nvidia•com,
	jiri@nvidia•com
Subject: Re: [PATCH net-next 0/6] selftests: mlxsw: Fixes
Date: Fri, 23 Apr 2021 21:10:16 +0000	[thread overview]
Message-ID: <161921221622.24005.11828493414067253441.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1619179926.git.petrm@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri, 23 Apr 2021 14:19:42 +0200 you wrote:
> This patch set carries fixes to selftest issues that we have hit in our
> nightly regression run. Almost all are in mlxsw selftests, though one is in
> a generic forwarding selftest.
> 
> - In patch #1, in an ERSPAN test, install an FDB entry as static instead of
>   (implicitly) as local.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] selftests: net: mirror_gre_vlan_bridge_1q: Make an FDB entry static
    https://git.kernel.org/netdev/net-next/c/c8d0260cdd96
  - [net-next,2/6] selftests: mlxsw: Remove a redundant if statement in port_scale test
    https://git.kernel.org/netdev/net-next/c/b6fc2f212108
  - [net-next,3/6] selftests: mlxsw: Remove a redundant if statement in tc_flower_scale test
    https://git.kernel.org/netdev/net-next/c/1f1c92139e36
  - [net-next,4/6] selftests: mlxsw: Return correct error code in resource scale tests
    https://git.kernel.org/netdev/net-next/c/059b18e21c63
  - [net-next,5/6] selftests: mlxsw: Increase the tolerance of backlog buildup
    https://git.kernel.org/netdev/net-next/c/dda7f4fa5583
  - [net-next,6/6] selftests: mlxsw: Fix mausezahn invocation in ERSPAN scale test
    https://git.kernel.org/netdev/net-next/c/1233898ab758

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



      parent reply	other threads:[~2021-04-23 21:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 12:19 [PATCH net-next 0/6] selftests: mlxsw: Fixes Petr Machata
2021-04-23 12:19 ` [PATCH net-next 1/6] selftests: net: mirror_gre_vlan_bridge_1q: Make an FDB entry static Petr Machata
2021-04-23 12:19 ` [PATCH net-next 2/6] selftests: mlxsw: Remove a redundant if statement in port_scale test Petr Machata
2021-04-23 12:19 ` [PATCH net-next 3/6] selftests: mlxsw: Remove a redundant if statement in tc_flower_scale test Petr Machata
2021-04-23 12:19 ` [PATCH net-next 4/6] selftests: mlxsw: Return correct error code in resource scale tests Petr Machata
2021-04-23 12:19 ` [PATCH net-next 5/6] selftests: mlxsw: Increase the tolerance of backlog buildup Petr Machata
2021-04-23 12:19 ` [PATCH net-next 6/6] selftests: mlxsw: Fix mausezahn invocation in ERSPAN scale test Petr Machata
2021-04-23 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=161921221622.24005.11828493414067253441.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=danieller@nvidia$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=idosch@nvidia$(echo .)com \
    --cc=jiri@nvidia$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=mlxsw@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=petrm@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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