From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
kuba@kernel.org, davem@davemloft.net,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next 0/6] Add support for LAN937x T1 Phy Driver
Date: Fri, 04 Mar 2022 12:50:11 +0000 [thread overview]
Message-ID: <164639821165.27302.4276838745317071459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220304094401.31375-1-arun.ramadoss@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 4 Mar 2022 15:13:55 +0530 you wrote:
> LAN937x is a Multi-port 100Base-T1 Switch and it internally uses LAN87xx
> T1 Phy. This series of patch update the initialization routine for the
> LAN87xx phy and also add LAN937x part support. Added the T1 Phy
> master-slave configuration through ethtool.
>
> Arun Ramadoss (6):
> net: phy: used genphy_soft_reset for phy reset in LAN87xx
> net: phy: used the PHY_ID_MATCH_MODEL macro for LAN87XX
> net: phy: removed empty lines in LAN87XX
> net: phy: updated the initialization routine for LAN87xx
> net: phy: added the LAN937x phy support
> net: phy: added ethtool master-slave configuration support
>
> [...]
Here is the summary with links:
- [net-next,1/6] net: phy: used genphy_soft_reset for phy reset in LAN87xx
https://git.kernel.org/netdev/net-next/c/8eee3d353626
- [net-next,2/6] net: phy: used the PHY_ID_MATCH_MODEL macro for LAN87XX
https://git.kernel.org/netdev/net-next/c/79cea9a9c93a
- [net-next,3/6] net: phy: removed empty lines in LAN87XX
https://git.kernel.org/netdev/net-next/c/ccc8cc5badde
- [net-next,4/6] net: phy: updated the initialization routine for LAN87xx
https://git.kernel.org/netdev/net-next/c/8637034bc63f
- [net-next,5/6] net: phy: added the LAN937x phy support
https://git.kernel.org/netdev/net-next/c/680baca546f2
- [net-next,6/6] net: phy: added ethtool master-slave configuration support
https://git.kernel.org/netdev/net-next/c/8a1b415d70b7
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-03-04 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 9:43 [PATCH net-next 0/6] Add support for LAN937x T1 Phy Driver Arun Ramadoss
2022-03-04 9:43 ` [PATCH net-next 1/6] net: phy: used genphy_soft_reset for phy reset in LAN87xx Arun Ramadoss
2022-03-04 9:43 ` [PATCH net-next 2/6] net: phy: used the PHY_ID_MATCH_MODEL macro for LAN87XX Arun Ramadoss
2022-03-04 9:43 ` [PATCH net-next 3/6] net: phy: removed empty lines in LAN87XX Arun Ramadoss
2022-03-04 9:43 ` [PATCH net-next 4/6] net: phy: updated the initialization routine for LAN87xx Arun Ramadoss
2022-03-04 9:44 ` [PATCH net-next 5/6] net: phy: added the LAN937x phy support Arun Ramadoss
2022-03-04 9:44 ` [PATCH net-next 6/6] net: phy: added ethtool master-slave configuration support Arun Ramadoss
2022-03-04 13:13 ` Andrew Lunn
2022-03-04 13:31 ` Arun.Ramadoss
2022-03-04 13:51 ` Andrew Lunn
2022-03-04 12: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=164639821165.27302.4276838745317071459.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=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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 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).