From: patchwork-bot+netdevbpf@kernel.org
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] Add Xilinx GMII2RGMII loopback support
Date: Fri, 20 Aug 2021 13:40:08 +0000 [thread overview]
Message-ID: <162946680867.23508.17751840651047181515.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210819131154.6586-1-gerhard@engleder-embedded.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 19 Aug 2021 15:11:51 +0200 you wrote:
> The Xilinx GMII2RGMII driver overrides PHY driver functions in order to
> configure the device according to the link speed of the PHY attached to
> it. This is implemented for a normal link but not for loopback.
>
> Andrew told me to use phy_loopback and this changes make phy_loopback
> work in combination with Xilinx GMII2RGMII.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] net: phy: Support set_loopback override
https://git.kernel.org/netdev/net-next/c/4ed311b08a91
- [net-next,v2,2/3] net: phy: Uniform PHY driver access
https://git.kernel.org/netdev/net-next/c/3ac8eed62596
- [net-next,v2,3/3] net: phy: gmii2rgmii: Support PHY loopback
https://git.kernel.org/netdev/net-next/c/ceaeaafc8b62
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:[~2021-08-20 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 13:11 [PATCH net-next v2 0/3] Add Xilinx GMII2RGMII loopback support Gerhard Engleder
2021-08-19 13:11 ` [PATCH net-next v2 1/3] net: phy: Support set_loopback override Gerhard Engleder
2021-08-19 13:11 ` [PATCH net-next v2 2/3] net: phy: Uniform PHY driver access Gerhard Engleder
2021-08-19 13:11 ` [PATCH net-next v2 3/3] net: phy: gmii2rgmii: Support PHY loopback Gerhard Engleder
2021-08-20 13:40 ` 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=162946680867.23508.17751840651047181515.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=gerhard@engleder-embedded.com \
--cc=netdev@vger.kernel.org \
/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.