From: Florian Fainelli <f.fainelli@gmail.com>
To: Jian-Hong Pan <jhp@endlessos.org>
Cc: patchwork-bot+netdevbpf@kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
Doug Berger <opendmb@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
bcm-kernel-feedback-list@broadcom.com,
Linux Netdev List <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux@endlessos.org, linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v2] net: bcmgenet: Fix attaching to PYH failed on RPi 4B
Date: Wed, 23 Jun 2021 20:27:29 -0700 [thread overview]
Message-ID: <20eeedec-4ec2-7aae-2e80-09b784e1693b@gmail.com> (raw)
In-Reply-To: <CAPpJ_edpVxbnPBGTrkvB8EY5mt_sgPmoMv7rBdUKUHZJnjhHNg@mail.gmail.com>
On 6/23/2021 7:47 PM, Jian-Hong Pan wrote:
> Florian Fainelli <f.fainelli@gmail.com> 於 2021年6月24日 週四 上午5:19寫道:
>>
>> On 6/23/21 1:50 PM, patchwork-bot+netdevbpf@kernel.org wrote:
>>> Hello:
>>>
>>> This patch was applied to netdev/net.git (refs/heads/master):
>>>
>>> On Wed, 23 Jun 2021 11:28:03 +0800 you wrote:
>>>> The Broadcom UniMAC MDIO bus from mdio-bcm-unimac module comes too late.
>>>> So, GENET cannot find the ethernet PHY on UniMAC MDIO bus. This leads
>>>> GENET fail to attach the PHY as following log:
>>>>
>>>> bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
>>>> ...
>>>> could not attach to PHY
>>>> bcmgenet fd580000.ethernet eth0: failed to connect to PHY
>>>> uart-pl011 fe201000.serial: no DMA platform data
>>>> libphy: bcmgenet MII bus: probed
>>>> ...
>>>> unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
>>>>
>>>> [...]
>>>
>>> Here is the summary with links:
>>> - [v2] net: bcmgenet: Fix attaching to PYH failed on RPi 4B
>>> https://git.kernel.org/netdev/net/c/b2ac9800cfe0
>
> This bot is interesting!!! Good feature! :)
>
>> There was feedback given that could have deserved a v3, if nothing else
>> to fix the typo in the subject, I suppose that would do though.
>
> I can prepare the v3 patch with Florian's suggestion!
Too late, once it's merged only fixups can be accepted, and that does
not include commit messages, it's alright.
--
Florian
next prev parent reply other threads:[~2021-06-24 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 10:33 [PATCH] net: bcmgenet: Fix attaching to PYH failed on RPi 4B Jian-Hong Pan
2021-06-21 13:09 ` Andrew Lunn
2021-06-21 16:37 ` Florian Fainelli
2021-06-21 16:47 ` Florian Fainelli
2021-06-21 16:56 ` Peter Robinson
2021-06-21 20:15 ` Stefan Wahren
2021-06-21 21:47 ` Florian Fainelli
2021-06-22 6:29 ` Jian-Hong Pan
2021-06-22 6:50 ` Heiner Kallweit
2021-06-22 7:46 ` Jian-Hong Pan
2021-06-23 3:28 ` [PATCH v2] " Jian-Hong Pan
2021-06-23 4:00 ` Florian Fainelli
2021-06-23 20:50 ` patchwork-bot+netdevbpf
2021-06-23 21:19 ` Florian Fainelli
2021-06-24 2:47 ` Jian-Hong Pan
2021-06-24 3:27 ` Florian Fainelli [this message]
2021-06-24 3:28 ` Jian-Hong Pan
2021-06-24 3:22 ` [PATCH v3] net: bcmgenet: Add mdio-bcm-unimac soft dependency Jian-Hong Pan
2021-06-24 23:00 ` 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=20eeedec-4ec2-7aae-2e80-09b784e1693b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jhp@endlessos.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@endlessos.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=stefan.wahren@i2se.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).