public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, ramon.nordin.rodriguez@ferroamp.se,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	parthiban.veerasooran@microchip.com,
	UNGLinuxDriver@microchip.com, Thorsten.Kummermehr@microchip.com
Subject: Re: [PATCH net-next v4 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver
Date: Fri, 11 Oct 2024 23:10:48 +0000	[thread overview]
Message-ID: <172868824823.3022673.9404105689070586196.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241010082205.221493-1-parthiban.veerasooran@microchip.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 10 Oct 2024 13:51:58 +0530 you wrote:
> This patch series contain the below updates:
> - Restructured lan865x_write_cfg_params() and lan865x_read_cfg_params()
>   functions arguments to more generic.
> - Updated new/improved initial settings of LAN865X Rev.B0 from latest
>   AN1760.
> - Added support for LAN865X Rev.B1 from latest AN1760.
> - Moved LAN867X reset handling to a new function for flexibility.
> - Added support for LAN867X Rev.C1/C2 from latest AN1699.
> - Disabled/enabled collision detection based on PLCA setting.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/7] net: phy: microchip_t1s: restructure cfg read/write functions arguments
    https://git.kernel.org/netdev/net-next/c/9826b9a08b9c
  - [net-next,v4,2/7] net: phy: microchip_t1s: update new initial settings for LAN865X Rev.B0
    https://git.kernel.org/netdev/net-next/c/d793beee2d80
  - [net-next,v4,3/7] net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1
    https://git.kernel.org/netdev/net-next/c/7a0414fdccf3
  - [net-next,v4,4/7] net: phy: microchip_t1s: move LAN867X reset handling to a new function
    https://git.kernel.org/netdev/net-next/c/117b70e4c67b
  - [net-next,v4,5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1
    https://git.kernel.org/netdev/net-next/c/662d9c5fe19d
  - [net-next,v4,6/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2
    https://git.kernel.org/netdev/net-next/c/6b079d8f7b95
  - [net-next,v4,7/7] net: phy: microchip_t1s: configure collision detection based on PLCA mode
    https://git.kernel.org/netdev/net-next/c/78341049fbcd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-10-11 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  8:21 [PATCH net-next v4 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2024-10-10  8:21 ` [PATCH net-next v4 1/7] net: phy: microchip_t1s: restructure cfg read/write functions arguments Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 2/7] net: phy: microchip_t1s: update new initial settings for LAN865X Rev.B0 Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 3/7] net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1 Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 4/7] net: phy: microchip_t1s: move LAN867X reset handling to a new function Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1 Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 6/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2 Parthiban Veerasooran
2024-10-10  8:22 ` [PATCH net-next v4 7/7] net: phy: microchip_t1s: configure collision detection based on PLCA mode Parthiban Veerasooran
2024-10-11 23: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=172868824823.3022673.9404105689070586196.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Parthiban.Veerasooran@microchip.com \
    --cc=Thorsten.Kummermehr@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ramon.nordin.rodriguez@ferroamp.se \
    /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