From: patchwork-bot+netdevbpf@kernel.org
To: Jerry Ray <jerry.ray@microchip.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux@armlinux.org.uk, jbe@pengutronix.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next: PATCH v7 0/7] dsa: lan9303: Move to PHYLINK
Date: Fri, 20 Jan 2023 09:00:18 +0000 [thread overview]
Message-ID: <167420521875.28394.1687143741537531165.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230117205703.25960-1-jerry.ray@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 17 Jan 2023 14:56:56 -0600 you wrote:
> This patch series moves the lan9303 driver to use the phylink
> api away from phylib.
>
> Migrating to phylink means removing the .adjust_link api. The
> functionality from the adjust_link is moved to the phylink_mac_link_up
> api. The code being removed only affected the cpu port. The other
> ports on the LAN9303 do not need anything from the phylink_mac_link_up
> api.
>
> [...]
Here is the summary with links:
- [net-next:,v7,1/7] dsa: lan9303: align dsa_switch_ops members
https://git.kernel.org/netdev/net-next/c/9755126dc038
- [net-next:,v7,2/7] dsa: lan9303: move Turbo Mode bit init
https://git.kernel.org/netdev/net-next/c/1bcb5df81e4b
- [net-next:,v7,3/7] dsa: lan9303: Add exception logic for read failure
https://git.kernel.org/netdev/net-next/c/601f574a1b44
- [net-next:,v7,4/7] dsa: lan9303: write reg only if necessary
https://git.kernel.org/netdev/net-next/c/de375aa860fb
- [net-next:,v7,5/7] dsa: lan9303: Port 0 is xMII port
https://git.kernel.org/netdev/net-next/c/56e23d91bcfd
- [net-next:,v7,6/7] dsa: lan9303: Migrate to PHYLINK
https://git.kernel.org/netdev/net-next/c/332bc552a402
- [net-next:,v7,7/7] dsa: lan9303: Add flow ctrl in link_up
https://git.kernel.org/netdev/net-next/c/87523986570e
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:[~2023-01-20 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 20:56 [net-next: PATCH v7 0/7] dsa: lan9303: Move to PHYLINK Jerry Ray
2023-01-17 20:56 ` [net-next: PATCH v7 1/7] dsa: lan9303: align dsa_switch_ops members Jerry Ray
2023-01-17 20:56 ` [net-next: PATCH v7 2/7] dsa: lan9303: move Turbo Mode bit init Jerry Ray
2023-01-17 20:56 ` [net-next: PATCH v7 3/7] dsa: lan9303: Add exception logic for read failure Jerry Ray
2023-01-17 20:57 ` [net-next: PATCH v7 4/7] dsa: lan9303: write reg only if necessary Jerry Ray
2023-01-17 20:57 ` [net-next: PATCH v7 5/7] dsa: lan9303: Port 0 is xMII port Jerry Ray
2023-01-17 20:57 ` [net-next: PATCH v7 6/7] dsa: lan9303: Migrate to PHYLINK Jerry Ray
2023-01-17 20:57 ` [net-next: PATCH v7 7/7] dsa: lan9303: Add flow ctrl in link_up Jerry Ray
2023-01-20 9: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=167420521875.28394.1687143741537531165.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jbe@pengutronix.de \
--cc=jerry.ray@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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