From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk
Subject: Re: [Patch net-next 00/11] net: dsa: microchip: common spi probe for the ksz series switches - part 1
Date: Tue, 21 Jun 2022 13:50:14 +0000 [thread overview]
Message-ID: <165581941490.20739.3823115591202055805.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220617084255.19376-1-arun.ramadoss@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 17 Jun 2022 14:12:44 +0530 you wrote:
> This patch series aims to refactor the ksz_switch_register routine to have the
> common flow for the ksz series switch. At present ksz8795.c & ksz9477.c have
> its own dsa_switch_ops and switch detect functionality.
> In ksz_switch_register, ksz_dev_ops is assigned based on the function parameter
> passed by the individual ksz8/ksz9477 switch register function. And then switch
> detect is performed based on the ksz_dev_ops.detect hook. This patch modifies
> the ksz_switch_register such a way that switch detect is performed first, based
> on the chip ksz_dev_ops is assigned to ksz_device structure. It ensures the
> common flow for the existing as well as LAN937x switches.
> In the next series of patch, it will move ksz_dsa_ops and dsa_switch_ops
> from ksz8795.c and ksz9477.c to ksz_common.c and have the common spi
> probe all the ksz based switches.
>
> [...]
Here is the summary with links:
- [net-next,01/11] net: dsa: microchip: ksz9477: cleanup the ksz9477_switch_detect
https://git.kernel.org/netdev/net-next/c/27faa0aa85f6
- [net-next,02/11] net: dsa: microchip: move switch chip_id detection to ksz_common
https://git.kernel.org/netdev/net-next/c/91a98917a883
- [net-next,03/11] net: dsa: microchip: move tag_protocol to ksz_common
https://git.kernel.org/netdev/net-next/c/534a0431e9e6
- [net-next,04/11] net: dsa: microchip: ksz9477: use ksz_read_phy16 & ksz_write_phy16
https://git.kernel.org/netdev/net-next/c/930e579083d7
- [net-next,05/11] net: dsa: microchip: move vlan functionality to ksz_common
https://git.kernel.org/netdev/net-next/c/f0d997e31bb3
- [net-next,06/11] net: dsa: microchip: move the port mirror to ksz_common
https://git.kernel.org/netdev/net-next/c/00a298bbc238
- [net-next,07/11] net: dsa: microchip: get P_STP_CTRL in ksz_port_stp_state by ksz_dev_ops
https://git.kernel.org/netdev/net-next/c/e593df51ffe8
- [net-next,08/11] net: dsa: microchip: update the ksz_phylink_get_caps
https://git.kernel.org/netdev/net-next/c/7012033ce10e
- [net-next,09/11] net: dsa: microchip: update the ksz_port_mdb_add/del
https://git.kernel.org/netdev/net-next/c/980c7d171d3a
- [net-next,10/11] net: dsa: microchip: update fdb add/del/dump in ksz_common
https://git.kernel.org/netdev/net-next/c/e587be759e6e
- [net-next,11/11] net: dsa: microchip: move get_phy_flags & mtu to ksz_common
https://git.kernel.org/netdev/net-next/c/1fe94f542e66
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:[~2022-06-21 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:42 [Patch net-next 00/11] net: dsa: microchip: common spi probe for the ksz series switches - part 1 Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 01/11] net: dsa: microchip: ksz9477: cleanup the ksz9477_switch_detect Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 02/11] net: dsa: microchip: move switch chip_id detection to ksz_common Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 03/11] net: dsa: microchip: move tag_protocol " Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 04/11] net: dsa: microchip: ksz9477: use ksz_read_phy16 & ksz_write_phy16 Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 05/11] net: dsa: microchip: move vlan functionality to ksz_common Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 06/11] net: dsa: microchip: move the port mirror " Arun Ramadoss
2022-06-17 22:03 ` Florian Fainelli
2022-06-17 8:42 ` [Patch net-next 07/11] net: dsa: microchip: get P_STP_CTRL in ksz_port_stp_state by ksz_dev_ops Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 08/11] net: dsa: microchip: update the ksz_phylink_get_caps Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 09/11] net: dsa: microchip: update the ksz_port_mdb_add/del Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 10/11] net: dsa: microchip: update fdb add/del/dump in ksz_common Arun Ramadoss
2022-06-17 8:42 ` [Patch net-next 11/11] net: dsa: microchip: move get_phy_flags & mtu to ksz_common Arun Ramadoss
2022-06-21 11:18 ` [Patch net-next 00/11] net: dsa: microchip: common spi probe for the ksz series switches - part 1 Vladimir Oltean
2022-06-21 13:50 ` 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=165581941490.20739.3823115591202055805.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox