From: patchwork-bot+netdevbpf@kernel.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: hauke@hauke-m.de, netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: lantiq: Wait for the GPHY firmware to be ready
Date: Mon, 16 Nov 2020 21:50:05 +0000 [thread overview]
Message-ID: <160556340543.26491.18312190727350290865.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201115165757.552641-1-martin.blumenstingl@googlemail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sun, 15 Nov 2020 17:57:57 +0100 you wrote:
> A user reports (slightly shortened from the original message):
> libphy: lantiq,xrx200-mdio: probed
> mdio_bus 1e108000.switch-mii: MDIO device at address 17 is missing.
> gswip 1e108000.switch lan: no phy at 2
> gswip 1e108000.switch lan: failed to connect to port 2: -19
> lantiq,xrx200-net 1e10b308.eth eth0: error -19 setting up slave phy
>
> [...]
Here is the summary with links:
- [v2] net: lantiq: Wait for the GPHY firmware to be ready
https://git.kernel.org/netdev/net/c/2a1828e378c1
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:[~2020-11-16 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 16:57 [PATCH v2] net: lantiq: Wait for the GPHY firmware to be ready Martin Blumenstingl
2020-11-15 17:07 ` Hauke Mehrtens
2020-11-16 2:57 ` Florian Fainelli
2020-11-16 14:38 ` Andrew Lunn
2020-11-16 21:50 ` 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=160556340543.26491.18312190727350290865.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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