From: patchwork-bot+netdevbpf@kernel.org
To: Robert Marko <robimarko@gmail.com>
Cc: andersson@kernel.org, konrad.dybcio@linaro.org, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: phy: qcom: qca808x: fill in possible_interfaces
Date: Fri, 01 Mar 2024 09:00:29 +0000 [thread overview]
Message-ID: <170928362991.25916.1636738478818920019.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240228172452.2456842-1-robimarko@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 28 Feb 2024 18:24:08 +0100 you wrote:
> QCA808x does not currently fill in the possible_interfaces.
>
> This leads to Phylink not being aware that it supports 2500Base-X as well
> so in cases where it is connected to a DSA switch like MV88E6393 it will
> limit that port to phy-mode set in the DTS.
>
> That means that if SGMII is used you are limited to 1G only while if
> 2500Base-X was set you are limited to 2.5G only.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: phy: qcom: qca808x: add helper for checking for 1G only model
https://git.kernel.org/netdev/net-next/c/f058b2dd70b1
- [net-next,v2,2/2] net: phy: qcom: qca808x: fill in possible_interfaces
https://git.kernel.org/netdev/net-next/c/cb28f7029606
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:[~2024-03-01 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:24 [PATCH net-next v2 0/2] net: phy: qcom: qca808x: fill in possible_interfaces Robert Marko
2024-02-28 17:24 ` [PATCH net-next v2 1/2] net: phy: qcom: qca808x: add helper for checking for 1G only model Robert Marko
2024-02-28 17:24 ` [PATCH net-next v2 2/2] net: phy: qcom: qca808x: fill in possible_interfaces Robert Marko
2024-02-28 18:04 ` Russell King (Oracle)
2024-03-01 9:00 ` 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=170928362991.25916.1636738478818920019.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robimarko@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;
as well as URLs for NNTP newsgroup(s).