From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, 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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] net: dsa: adjust_link removal
Date: Thu, 02 May 2024 02:20:31 +0000 [thread overview]
Message-ID: <171461643153.4262.10712563951125097802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240430164816.2400606-1-florian.fainelli@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Apr 2024 09:48:14 -0700 you wrote:
> Now that the last in-tree driver (b53) has been converted to PHYLINK, we
> can get rid of all of code that catered to working with drivers
> implementing only PHYLIB's adjust_link callback.
>
> Changes in v3:
>
> - removed additional code in dsa_port_phylink_mac_link_down pertaining
> to the phy_device reference
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: dsa: Remove fixed_link_update member
https://git.kernel.org/netdev/net-next/c/ad3e1287c6f3
- [net-next,v3,2/2] net: dsa: Remove adjust_link paths
https://git.kernel.org/netdev/net-next/c/8a021a863a7d
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-05-02 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 16:48 [PATCH net-next v3 0/2] net: dsa: adjust_link removal Florian Fainelli
2024-04-30 16:48 ` [PATCH net-next v3 1/2] net: dsa: Remove fixed_link_update member Florian Fainelli
2024-04-30 16:48 ` [PATCH net-next v3 2/2] net: dsa: Remove adjust_link paths Florian Fainelli
2024-04-30 16:55 ` [PATCH net-next v3 0/2] net: dsa: adjust_link removal Russell King (Oracle)
2024-05-02 2:20 ` 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=171461643153.4262.10712563951125097802.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=florian.fainelli@broadcom.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 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.