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, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lukas@wunner.de, linux@armlinux.org.uk
Subject: Re: [PATCH net-next v2 1/2] net: asix: ax88772: migrate to phylink
Date: Fri, 26 Aug 2022 09:20:15 +0000 [thread overview]
Message-ID: <166150561599.22218.15711919447360089727.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822123943.2409987-1-o.rempel@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 22 Aug 2022 14:39:42 +0200 you wrote:
> There are some exotic ax88772 based devices which may require
> functionality provide by the phylink framework. For example:
> - US100A20SFP, USB 2.0 auf LWL Converter with SFP Cage
> - AX88772B USB to 100Base-TX Ethernet (with RMII) demo board, where it
> is possible to switch between internal PHY and external RMII based
> connection.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: asix: ax88772: migrate to phylink
https://git.kernel.org/netdev/net-next/c/e0bffe3e6894
- [net-next,v2,2/2] net: asix: ax88772: add ethtool pause configuration
https://git.kernel.org/netdev/net-next/c/6661918c3b59
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:[~2022-08-26 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 12:39 [PATCH net-next v2 1/2] net: asix: ax88772: migrate to phylink Oleksij Rempel
2022-08-22 12:39 ` [PATCH net-next v2 2/2] net: asix: ax88772: add ethtool pause configuration Oleksij Rempel
2022-08-25 21:18 ` Andrew Lunn
2022-08-26 9: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=166150561599.22218.15711919447360089727.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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