From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, woojung.huh@microchip.com,
andrew+netdev@lunn.ch, rmk+kernel@armlinux.org.uk,
Thangaraj.S@microchip.com, Rengarajan.S@microchip.com,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
phil@raspberrypi.org, maxime.chevallier@bootlin.com,
horms@kernel.org
Subject: Re: [PATCH net-next v8 0/7] lan78xx: preparation for PHYLINK conversion
Date: Wed, 07 May 2025 12:00:37 +0000 [thread overview]
Message-ID: <174661923750.2198858.15834248841787525369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250505084341.824165-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 5 May 2025 10:43:34 +0200 you wrote:
> This patch series contains the first part of the LAN78xx driver
> refactoring in preparation for converting the driver to use the PHYLINK
> framework.
>
> The goal of this initial part is to reduce the size and complexity of
> the final PHYLINK conversion by introducing incremental cleanups and
> logical separation of concerns, such as:
>
> [...]
Here is the summary with links:
- [net-next,v8,1/7] net: usb: lan78xx: Improve error handling in PHY initialization
https://git.kernel.org/netdev/net-next/c/232aa459aa40
- [net-next,v8,2/7] net: usb: lan78xx: remove explicit check for missing PHY driver
https://git.kernel.org/netdev/net-next/c/3da0ae52705d
- [net-next,v8,3/7] net: usb: lan78xx: refactor PHY init to separate detection and MAC configuration
https://git.kernel.org/netdev/net-next/c/d39f339d2603
- [net-next,v8,4/7] net: usb: lan78xx: move LED DT configuration to helper
https://git.kernel.org/netdev/net-next/c/8ba1f33c55d2
- [net-next,v8,5/7] net: usb: lan78xx: Extract PHY interrupt acknowledgment to helper
https://git.kernel.org/netdev/net-next/c/f485849a381f
- [net-next,v8,6/7] net: usb: lan78xx: Refactor USB link power configuration into helper
https://git.kernel.org/netdev/net-next/c/d746e0740b28
- [net-next,v8,7/7] net: usb: lan78xx: Extract flow control configuration to helper
https://git.kernel.org/netdev/net-next/c/ef6a29e86785
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:[~2025-05-07 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 8:43 Oleksij Rempel
2025-05-05 8:43 ` [PATCH net-next v8 1/7] net: usb: lan78xx: Improve error handling in PHY initialization Oleksij Rempel
2025-05-07 3:56 ` Thangaraj.S
2025-05-05 8:43 ` [PATCH net-next v8 2/7] net: usb: lan78xx: remove explicit check for missing PHY driver Oleksij Rempel
2025-05-07 3:57 ` Thangaraj.S
2025-05-05 8:43 ` [PATCH net-next v8 3/7] net: usb: lan78xx: refactor PHY init to separate detection and MAC configuration Oleksij Rempel
2025-05-06 5:31 ` Thangaraj.S
2025-05-06 10:13 ` Oleksij Rempel
2025-05-07 3:58 ` Thangaraj.S
2025-05-05 8:43 ` [PATCH net-next v8 4/7] net: usb: lan78xx: move LED DT configuration to helper Oleksij Rempel
2025-05-07 3:59 ` Thangaraj.S
2025-05-05 8:43 ` [PATCH net-next v8 5/7] net: usb: lan78xx: Extract PHY interrupt acknowledgment " Oleksij Rempel
2025-05-07 3:59 ` Thangaraj.S
2025-05-05 8:43 ` [PATCH net-next v8 6/7] net: usb: lan78xx: Refactor USB link power configuration into helper Oleksij Rempel
2025-05-05 8:43 ` [PATCH net-next v8 7/7] net: usb: lan78xx: Extract flow control configuration to helper Oleksij Rempel
2025-05-07 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=174661923750.2198858.15834248841787525369.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=rmk+kernel@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®