From: patchwork-bot+netdevbpf@kernel.org
To: Sit@ci.codeaurora.org, Michael Wei Hong <michael.wei.hong.sit@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
boon.leong.ong@intel.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
hkallweit1@gmail.com, andrew@lunn.ch,
martin.blumenstingl@googlemail.com, Shahab.Vahedi@synopsys.com,
m.szyprowski@samsung.com, hong.aun.looi@intel.com,
weifeng.voon@intel.com, peter.jun.ann.lai@intel.com,
muhammad.husaini.zulkifli@intel.com, tee.min.tan@intel.com,
hock.leong.kweh@intel.com
Subject: Re: [RESEND PATCH net 1/1] net: stmmac: check fwnode for phy device before scanning for phy
Date: Thu, 06 Apr 2023 15:20:17 +0000 [thread overview]
Message-ID: <168079441791.8535.15515583518065122316.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406024541.3556305-1-michael.wei.hong.sit@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Apr 2023 10:45:41 +0800 you wrote:
> Some DT devices already have phy device configured in the DT/ACPI.
> Current implementation scans for a phy unconditionally even though
> there is a phy listed in the DT/ACPI and already attached.
>
> We should check the fwnode if there is any phy device listed in
> fwnode and decide whether to scan for a phy to attach to.
>
> [...]
Here is the summary with links:
- [RESEND,net,1/1] net: stmmac: check fwnode for phy device before scanning for phy
https://git.kernel.org/netdev/net/c/8fbc10b995a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Sit@ci.codeaurora.org, Michael Wei Hong <michael.wei.hong.sit@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
boon.leong.ong@intel.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
hkallweit1@gmail.com, andrew@lunn.ch,
martin.blumenstingl@googlemail.com, Shahab.Vahedi@synopsys.com,
m.szyprowski@samsung.com, hong.aun.looi@intel.com,
weifeng.voon@intel.com, peter.jun.ann.lai@intel.com,
muhammad.husaini.zulkifli@intel.com, tee.min.tan@intel.com,
hock.leong.kweh@intel.com
Subject: Re: [RESEND PATCH net 1/1] net: stmmac: check fwnode for phy device before scanning for phy
Date: Thu, 06 Apr 2023 15:20:17 +0000 [thread overview]
Message-ID: <168079441791.8535.15515583518065122316.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406024541.3556305-1-michael.wei.hong.sit@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Apr 2023 10:45:41 +0800 you wrote:
> Some DT devices already have phy device configured in the DT/ACPI.
> Current implementation scans for a phy unconditionally even though
> there is a phy listed in the DT/ACPI and already attached.
>
> We should check the fwnode if there is any phy device listed in
> fwnode and decide whether to scan for a phy to attach to.
>
> [...]
Here is the summary with links:
- [RESEND,net,1/1] net: stmmac: check fwnode for phy device before scanning for phy
https://git.kernel.org/netdev/net/c/8fbc10b995a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-06 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 2:45 [RESEND PATCH net 1/1] net: stmmac: check fwnode for phy device before scanning for phy Michael Sit Wei Hong
2023-04-06 2:45 ` Michael Sit Wei Hong
2023-04-06 14:25 ` Jakub Kicinski
2023-04-06 14:25 ` Jakub Kicinski
2023-04-06 14:40 ` Sit, Michael Wei Hong
2023-04-06 14:40 ` Sit, Michael Wei Hong
2023-04-06 15:20 ` patchwork-bot+netdevbpf [this message]
2023-04-06 15:20 ` patchwork-bot+netdevbpf
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=168079441791.8535.15515583518065122316.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Shahab.Vahedi@synopsys.com \
--cc=Sit@ci.codeaurora.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=hock.leong.kweh@intel.com \
--cc=hong.aun.looi@intel.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=peter.jun.ann.lai@intel.com \
--cc=tee.min.tan@intel.com \
--cc=weifeng.voon@intel.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.