From: patchwork-bot+netdevbpf@kernel.org
To: Yijie Yang <quic_yijiyang@quicinc.com>
Cc: vkoul@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
krzysztof.kozlowski@linaro.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: net: qcom,ethqos: Correct fallback compatible for qcom,qcs615-ethqos
Date: Thu, 23 Jan 2025 04:10:31 +0000 [thread overview]
Message-ID: <173760543124.917319.17863724148091129767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250120-schema_qcs615-v4-1-d9d122f89e64@quicinc.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 20 Jan 2025 15:08:28 +0800 you wrote:
> The qcs615-ride utilizes the same EMAC as the qcs404, rather than the
> sm8150. The current incorrect fallback could result in packet loss.
> The Ethernet on qcs615-ride is currently not utilized by anyone. Therefore,
> there is no need to worry about any ABI impact.
>
> Fixes: 32535b9410b8 ("dt-bindings: net: qcom,ethqos: add description for qcs615")
> Signed-off-by: Yijie Yang <quic_yijiyang@quicinc.com>
>
> [...]
Here is the summary with links:
- [v4] dt-bindings: net: qcom,ethqos: Correct fallback compatible for qcom,qcs615-ethqos
https://git.kernel.org/netdev/net/c/ba1af257a057
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:[~2025-01-23 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 7:08 [PATCH v4] dt-bindings: net: qcom,ethqos: Correct fallback compatible for qcom,qcs615-ethqos Yijie Yang
2025-01-20 7:37 ` Krzysztof Kozlowski
2025-01-23 4:10 ` 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=173760543124.917319.17863724148091129767.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_yijiyang@quicinc.com \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
/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