From: patchwork-bot+netdevbpf@kernel.org
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, lxu@maxlinear.com,
hkallweit1@gmail.com, pabeni@redhat.com, edumazet@google.com,
linux@armlinux.org.uk, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, Ian.Saturley@microchip.com
Subject: Re: [PATCH net-next V1 0/2] net: phy: mxl-gpy: Add MDI-X
Date: Fri, 28 Oct 2022 10:20:17 +0000 [thread overview]
Message-ID: <166695241746.31704.11349157920416012770.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026055918.4225-1-Raju.Lakkaraju@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 26 Oct 2022 11:29:16 +0530 you wrote:
> This patch series add the MDI-X feature to GPY211 PHYs and
> Also Change return type to gpy_update_interface() function
>
> Raju Lakkaraju (2):
> net: phy: mxl-gpy: Change gpy_update_interface() function return type
> net: phy: mxl-gpy: Add PHY Auto/MDI/MDI-X set driver for GPY211 chips
>
> [...]
Here is the summary with links:
- [net-next,V1,1/2] net: phy: mxl-gpy: Change gpy_update_interface() function return type
https://git.kernel.org/netdev/net-next/c/7a495dde27eb
- [net-next,V1,2/2] net: phy: mxl-gpy: Add PHY Auto/MDI/MDI-X set driver for GPY211 chips
https://git.kernel.org/netdev/net-next/c/fd8825cd8c6f
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-10-28 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 5:59 [PATCH net-next V1 0/2] net: phy: mxl-gpy: Add MDI-X Raju Lakkaraju
2022-10-26 5:59 ` [PATCH net-next V1 1/2] net: phy: mxl-gpy: Change gpy_update_interface() function return type Raju Lakkaraju
2022-10-26 5:59 ` [PATCH net-next V1 2/2] net: phy: mxl-gpy: Add PHY Auto/MDI/MDI-X set driver for GPY211 chips Raju Lakkaraju
2022-10-28 10: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=166695241746.31704.11349157920416012770.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ian.Saturley@microchip.com \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).