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, danieller@nvidia.com, mlxsw@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next v2 0/2] mlxsw: Expose number of physical ports
Date: Sat, 23 Jan 2021 06:10:23 +0000 [thread overview]
Message-ID: <161138222376.25900.4792043766515391595.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210121131024.2656154-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 21 Jan 2021 15:10:22 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The switch ASIC has a limited capacity of physical ports that it can
> support. While each system is brought up with a different number of
> ports, this number can be increased via splitting up to the ASIC's
> limit.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] mlxsw: Register physical ports as a devlink resource
https://git.kernel.org/netdev/net-next/c/321f7ab0d458
- [net-next,v2,2/2] selftests: mlxsw: Add a scale test for physical ports
https://git.kernel.org/netdev/net-next/c/5154b1b826d9
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-01-23 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:10 [PATCH net-next v2 0/2] mlxsw: Expose number of physical ports Ido Schimmel
2021-01-21 13:10 ` [PATCH net-next v2 1/2] mlxsw: Register physical ports as a devlink resource Ido Schimmel
2021-01-21 13:10 ` [PATCH net-next v2 2/2] selftests: mlxsw: Add a scale test for physical ports Ido Schimmel
2021-01-23 6: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=161138222376.25900.4792043766515391595.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danieller@nvidia.com \
--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 \
/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.