From: "Sit, Michael Wei Hong" <michael.wei.hong.sit@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Shahab Vahedi <Shahab.Vahedi@synopsys.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"Looi, Hong Aun" <hong.aun.looi@intel.com>,
"Voon, Weifeng" <weifeng.voon@intel.com>,
"Lai, Peter Jun Ann" <peter.jun.ann.lai@intel.com>,
"Zulkifli,
Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>,
"Tan, Tee Min" <tee.min.tan@intel.com>,
"Kweh, Hock Leong" <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, 6 Apr 2023 14:40:36 +0000 [thread overview]
Message-ID: <8E023389-DDC8-48E4-99FC-94CAC9543788@intel.com> (raw)
In-Reply-To: <20230406072504.68e032e6@kernel.org>
> On 6 Apr 2023, at 10:30 PM, Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Thu, 6 Apr 2023 10:45:41 +0800 Michael Sit Wei Hong 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.
>
> Why did you resend this?
Fix a minor typo in commit message and also added the tags
next prev parent reply other threads:[~2023-04-06 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 2:45 Michael Sit Wei Hong
2023-04-06 14:25 ` Jakub Kicinski
2023-04-06 14:40 ` Sit, Michael Wei Hong [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=8E023389-DDC8-48E4-99FC-94CAC9543788@intel.com \
--to=michael.wei.hong.sit@intel.com \
--cc=Shahab.Vahedi@synopsys.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®