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, amcohen@nvidia.com, mlxsw@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next 00/10] mlxsw: Spectrum-4 preparations
Date: Wed, 01 Dec 2021 15:00:16 +0000 [thread overview]
Message-ID: <163837081669.15182.316558560943506127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211201081240.3767366-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 1 Dec 2021 10:12:30 +0200 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The Spectrum-4 ASIC will support more than 256 ports, unlike existing
> ASICs. As such, various device registers were extended with two
> additional bits to encode a 10 bit local port. In some cases, new
> (Version 2) registers were introduced.
>
> [...]
Here is the summary with links:
- [net-next,01/10] mlxsw: spectrum: Bump minimum FW version to xx.2010.1006
https://git.kernel.org/netdev/net-next/c/2cb310dc4402
- [net-next,02/10] mlxsw: reg: Remove unused functions
https://git.kernel.org/netdev/net-next/c/b25dea489b55
- [net-next,03/10] mlxsw: item: Add support for local_port field in a split form
https://git.kernel.org/netdev/net-next/c/fda39347d90f
- [net-next,04/10] mlxsw: reg: Align existing registers to use extended local_port field
https://git.kernel.org/netdev/net-next/c/fd24b29a1b74
- [net-next,05/10] mlxsw: reg: Increase 'port_num' field in PMTDB register
https://git.kernel.org/netdev/net-next/c/da56f1a0d2a5
- [net-next,06/10] mlxsw: reg: Adjust PPCNT register to support local port 255
https://git.kernel.org/netdev/net-next/c/242e696e035f
- [net-next,07/10] mlxsw: Use u16 for local_port field instead of u8
https://git.kernel.org/netdev/net-next/c/c934757d9000
- [net-next,08/10] mlxsw: Add support for more than 256 ports in SBSR register
https://git.kernel.org/netdev/net-next/c/f8538aec88b4
- [net-next,09/10] mlxsw: Use Switch Flooding Table Register Version 2
https://git.kernel.org/netdev/net-next/c/e86ad8ce5bed
- [net-next,10/10] mlxsw: Use Switch Multicast ID Register Version 2
https://git.kernel.org/netdev/net-next/c/51ef6b00798c
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-12-01 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 8:12 [PATCH net-next 00/10] mlxsw: Spectrum-4 preparations Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 01/10] mlxsw: spectrum: Bump minimum FW version to xx.2010.1006 Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 02/10] mlxsw: reg: Remove unused functions Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 03/10] mlxsw: item: Add support for local_port field in a split form Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 04/10] mlxsw: reg: Align existing registers to use extended local_port field Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 05/10] mlxsw: reg: Increase 'port_num' field in PMTDB register Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 06/10] mlxsw: reg: Adjust PPCNT register to support local port 255 Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 07/10] mlxsw: Use u16 for local_port field instead of u8 Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 08/10] mlxsw: Add support for more than 256 ports in SBSR register Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 09/10] mlxsw: Use Switch Flooding Table Register Version 2 Ido Schimmel
2021-12-01 8:12 ` [PATCH net-next 10/10] mlxsw: Use Switch Multicast ID " Ido Schimmel
2021-12-01 15:00 ` 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=163837081669.15182.316558560943506127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@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.