From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@armlinux.org.uk, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, linux@rempel-privat.de, marex@denx.de,
m.grzeschik@pengutronix.de, edumazet@google.com
Subject: Re: [Patch net-next 0/9] net: dsa: microchip: refactor the ksz switch init function
Date: Wed, 18 May 2022 12:00:16 +0000 [thread overview]
Message-ID: <165287521687.18230.9206117173490674365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220517094333.27225-1-arun.ramadoss@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 17 May 2022 15:13:24 +0530 you wrote:
> During the ksz_switch_register function, it calls the individual switches init
> functions (ksz8795.c and ksz9477.c). Both these functions have few things in
> common like, copying the chip specific data to struct ksz_dev, allocating
> ksz_port memory and mib_names memory & cnt. And to add the new LAN937x series
> switch, these allocations has to be replicated.
> Based on the review feedback of LAN937x part support patch, refactored the
> switch init function to move allocations to switch register.
>
> [...]
Here is the summary with links:
- [net-next,1/9] net: dsa: microchip: ksz8795: update the port_cnt value in ksz_chip_data
https://git.kernel.org/netdev/net-next/c/a30bf805592e
- [net-next,2/9] net: dsa: microchip: move ksz_chip_data to ksz_common
https://git.kernel.org/netdev/net-next/c/462d525018f0
- [net-next,3/9] net: dsa: microchip: perform the compatibility check for dev probed
https://git.kernel.org/netdev/net-next/c/eee16b147121
- [net-next,4/9] net: dsa: microchip: move struct mib_names to ksz_chip_data
https://git.kernel.org/netdev/net-next/c/a530e6f2204a
- [net-next,5/9] net: dsa: microchip: move port memory allocation to ksz_common
https://git.kernel.org/netdev/net-next/c/198b34783ab1
- [net-next,6/9] net: dsa: microchip: move get_strings to ksz_common
https://git.kernel.org/netdev/net-next/c/997d2126ac61
- [net-next,7/9] net: dsa: move mib->cnt_ptr reset code to ksz_common.c
https://git.kernel.org/netdev/net-next/c/b094c679662c
- [net-next,8/9] net: dsa: microchip: add the phylink get_caps
https://git.kernel.org/netdev/net-next/c/65ac79e18120
- [net-next,9/9] net: dsa: microchip: remove unused members in ksz_device
https://git.kernel.org/netdev/net-next/c/008db08b64f4
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-05-18 12:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 9:43 [Patch net-next 0/9] net: dsa: microchip: refactor the ksz switch init function Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 1/9] net: dsa: microchip: ksz8795: update the port_cnt value in ksz_chip_data Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 2/9] net: dsa: microchip: move ksz_chip_data to ksz_common Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 3/9] net: dsa: microchip: perform the compatibility check for dev probed Arun Ramadoss
2022-05-18 11:51 ` Vladimir Oltean
2022-05-17 9:43 ` [Patch net-next 4/9] net: dsa: microchip: move struct mib_names to ksz_chip_data Arun Ramadoss
2022-05-18 11:52 ` Vladimir Oltean
2022-05-17 9:43 ` [Patch net-next 5/9] net: dsa: microchip: move port memory allocation to ksz_common Arun Ramadoss
2022-05-18 12:02 ` Vladimir Oltean
2022-05-17 9:43 ` [Patch net-next 6/9] net: dsa: microchip: move get_strings " Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 7/9] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 8/9] net: dsa: microchip: add the phylink get_caps Arun Ramadoss
2022-05-17 9:43 ` [Patch net-next 9/9] net: dsa: microchip: remove unused members in ksz_device Arun Ramadoss
2022-05-18 12: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=165287521687.18230.9206117173490674365.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=linux@rempel-privat.de \
--cc=m.grzeschik@pengutronix.de \
--cc=marex@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).