From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jiri@nvidia.com, petrm@nvidia.com, mlxsw@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next 0/3] selftests: mlxsw: Various updates
Date: Mon, 25 Oct 2021 13:20:08 +0000 [thread overview]
Message-ID: <163516800855.2904.2219626049407594313.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211024071911.1064322-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 24 Oct 2021 10:19:08 +0300 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> This patchset contains various updates to mlxsw selftests.
>
> Patch #1 replaces open-coded compatibility checks with dedicated
> helpers. These helpers are used to skip tests when run on incompatible
> machines.
>
> [...]
Here is the summary with links:
- [net-next,1/3] selftests: mlxsw: Add helpers for skipping selftests
https://git.kernel.org/netdev/net-next/c/b8bfafe43481
- [net-next,2/3] selftests: mlxsw: Use permanent neighbours instead of reachable ones
https://git.kernel.org/netdev/net-next/c/535ac9a5fba5
- [net-next,3/3] selftests: mlxsw: Reduce test run time
https://git.kernel.org/netdev/net-next/c/e860419684b5
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:[~2021-10-25 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 7:19 [PATCH net-next 0/3] selftests: mlxsw: Various updates Ido Schimmel
2021-10-24 7:19 ` [PATCH net-next 1/3] selftests: mlxsw: Add helpers for skipping selftests Ido Schimmel
2021-10-24 7:19 ` [PATCH net-next 2/3] selftests: mlxsw: Use permanent neighbours instead of reachable ones Ido Schimmel
2021-10-24 7:19 ` [PATCH net-next 3/3] selftests: mlxsw: Reduce test run time Ido Schimmel
2021-10-25 13: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=163516800855.2904.2219626049407594313.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@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.