From: patchwork-bot+netdevbpf@kernel.org
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux@armlinux.org.uk, kuba@kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, richardcochran@gmail.com,
rdunlap@infradead.org, bryan.whitehead@microchip.com,
edumazet@google.com, pabeni@redhat.com,
maxime.chevallier@bootlin.com, linux-kernel@vger.kernel.org,
horms@kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next V6 0/5] Add support to PHYLINK for LAN743x/PCI11x1x chips
Date: Wed, 11 Sep 2024 10:10:31 +0000 [thread overview]
Message-ID: <172604943175.568857.6737661563582328586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240906103511.28416-1-Raju.Lakkaraju@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 6 Sep 2024 16:05:06 +0530 you wrote:
> This is the follow-up patch series of
> https://lkml.iu.edu/hypermail/linux/kernel/2310.2/02078.html
>
> Divide the PHYLINK adaptation and SFP modifications into two separate patch
> series.
>
> The current patch series focuses on transitioning the LAN743x driver's PHY
> support from phylib to phylink.
>
> [...]
Here is the summary with links:
- [net-next,V6,1/5] net: phylink: Add phylink_set_fixed_link() to configure fixed link state in phylink
https://git.kernel.org/netdev/net-next/c/4b3fc475c61f
- [net-next,V6,2/5] net: lan743x: Create separate PCS power reset function
https://git.kernel.org/netdev/net-next/c/ef0250456cc3
- [net-next,V6,3/5] net: lan743x: Create separate Link Speed Duplex state function
https://git.kernel.org/netdev/net-next/c/92b740a43fea
- [net-next,V6,4/5] net: lan743x: Migrate phylib to phylink
https://git.kernel.org/netdev/net-next/c/a5f199a8d8a0
- [net-next,V6,5/5] net: lan743x: Add support to ethtool phylink get and set settings
https://git.kernel.org/netdev/net-next/c/f95f28d794ed
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:[~2024-09-11 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:35 [PATCH net-next V6 0/5] Add support to PHYLINK for LAN743x/PCI11x1x chips Raju Lakkaraju
2024-09-06 10:35 ` [PATCH net-next V6 1/5] net: phylink: Add phylink_set_fixed_link() to configure fixed link state in phylink Raju Lakkaraju
2024-09-06 10:35 ` [PATCH net-next V6 2/5] net: lan743x: Create separate PCS power reset function Raju Lakkaraju
2024-09-06 10:35 ` [PATCH net-next V6 3/5] net: lan743x: Create separate Link Speed Duplex state function Raju Lakkaraju
2024-09-06 10:35 ` [PATCH net-next V6 4/5] net: lan743x: Migrate phylib to phylink Raju Lakkaraju
2024-09-17 15:59 ` Russell King (Oracle)
2024-09-06 10:35 ` [PATCH net-next V6 5/5] net: lan743x: Add support to ethtool phylink get and set settings Raju Lakkaraju
2024-09-11 10: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=172604943175.568857.6737661563582328586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richardcochran@gmail.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 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.