From: patchwork-bot+netdevbpf@kernel.org
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v3][net-next][PATCH 0/1] net: phy: Add link between phy dev and mac dev
Date: Thu, 01 Dec 2022 06:40:19 +0000 [thread overview]
Message-ID: <166987681924.1827.10288099850004190883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221130021216.1052230-1-xiaolei.wang@windriver.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Nov 2022 10:12:15 +0800 you wrote:
> Compared with v2, the comment of phydev->devlink is added, and the net-next tree is specified
>
> If the external phy used by current mac interface is
> managed by another mac interface, it means that this
> network port cannot work independently, especially
> when the system suspends and resumes, the following
> trace may appear, so we should create a device link
> between phy dev and mac dev.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/1] net: phy: Add link between phy dev and mac dev
https://git.kernel.org/netdev/net-next/c/bc66fa87d4fd
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-12-01 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:12 [v3][net-next][PATCH 0/1] net: phy: Add link between phy dev and mac dev Xiaolei Wang
2022-11-30 2:12 ` [v3][net-next][PATCH 1/1] " Xiaolei Wang
2022-11-30 17:13 ` Andrew Lunn
2022-11-30 20:11 ` Florian Fainelli
2022-12-01 6: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=166987681924.1827.10288099850004190883.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=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolei.wang@windriver.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).