From: patchwork-bot+netdevbpf@kernel.org
To: Greg Ungerer <gerg@kernel.org>
Cc: rmk+kernel@armlinux.org.uk, andrew@lunn.ch, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCHv2 1/2] net: dsa: mv88e6xxx: fix marvell 6350 switch probing
Date: Sun, 26 Nov 2023 11:40:23 +0000 [thread overview]
Message-ID: <170099882389.5867.3933796779624265445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231124041529.3450079-1-gerg@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Nov 2023 14:15:28 +1000 you wrote:
> As of commit de5c9bf40c45 ("net: phylink: require supported_interfaces to
> be filled") Marvell 88e6350 switches fail to be probed:
>
> ...
> mv88e6085 d0072004.mdio-mii:11: switch 0x3710 detected: Marvell 88E6350, revision 2
> mv88e6085 d0072004.mdio-mii:11: phylink: error: empty supported_interfaces
> error creating PHYLINK: -22
> mv88e6085: probe of d0072004.mdio-mii:11 failed with error -22
> ...
>
> [...]
Here is the summary with links:
- [PATCHv2,1/2] net: dsa: mv88e6xxx: fix marvell 6350 switch probing
https://git.kernel.org/netdev/net/c/b3f1a164c7f7
- [PATCHv2,2/2] net: dsa: mv88e6xxx: fix marvell 6350 probe crash
https://git.kernel.org/netdev/net/c/a524eabcd72d
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:[~2023-11-26 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 4:15 [PATCHv2 1/2] net: dsa: mv88e6xxx: fix marvell 6350 switch probing Greg Ungerer
2023-11-24 4:15 ` [PATCHv2 2/2] net: dsa: mv88e6xxx: fix marvell 6350 probe crash Greg Ungerer
2023-11-24 15:55 ` Andrew Lunn
2023-11-24 15:54 ` [PATCHv2 1/2] net: dsa: mv88e6xxx: fix marvell 6350 switch probing Andrew Lunn
2023-11-26 11: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=170099882389.5867.3933796779624265445.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerg@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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).