Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yijie Yang <quic_yijiyang@quicinc.com>,
	Vinod Koul <vkoul@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bhupesh Sharma <bhupesh.sharma@linaro.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org, quic_tingweiz@quicinc.com,
	quic_aiquny@quicinc.com,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 0/3] Add ethernet dts schema for qcs615/qcs8300
Date: Mon, 28 Oct 2024 12:04:30 +0100	[thread overview]
Message-ID: <132a8e29-3be7-422a-bc83-d6be00fac3e8@kernel.org> (raw)
In-Reply-To: <20241017-schema-v2-0-2320f68dc126@quicinc.com>

On 17/10/2024 11:52, Yijie Yang wrote:
> Document the ethernet and SerDes compatible for qcs8300. This platform
> shares the same EMAC and SerDes as sa8775p, so the compatible fallback to
> it.
> Document the ethernet compatible for qcs615. This platform shares the
> same EMAC as sm8150, so the compatible fallback to it.
> Document the compatible for revision 2 of the qcs8300-ride board.
> 
> Signed-off-by: Yijie Yang <quic_yijiyang@quicinc.com>
> ---
> This patch series depends on below patch series:
> https://lore.kernel.org/all/20240925-qcs8300_initial_dtsi-v2-0-494c40fa2a42@quicinc.com/
> https://lore.kernel.org/all/20240926-add_initial_support_for_qcs615-v3-0-e37617e91c62@quicinc.com/

So it cannot be merged...

Instead please decouple your works. I don't get why do you claim there
is dependency in the first place, but anyway. Fix up your patchsets to
fix that (if there is something to fix).

Best regards,
Krzysztof


  parent reply	other threads:[~2024-10-28 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  9:52 [PATCH v2 0/3] Add ethernet dts schema for qcs615/qcs8300 Yijie Yang
2024-10-17  9:52 ` [PATCH v2 1/3] dt-bindings: net: qcom,ethqos: add description for qcs615 Yijie Yang
2024-10-17  9:52 ` [PATCH v2 2/3] dt-bindings: phy: describe the Qualcomm SGMII PHY Yijie Yang
2024-10-17  9:52 ` [PATCH v2 3/3] dt-bindings: net: qcom,ethqos: add description for qcs8300 Yijie Yang
2024-10-28 11:04 ` Krzysztof Kozlowski [this message]
2024-10-29  2:17   ` [PATCH v2 0/3] Add ethernet dts schema for qcs615/qcs8300 Yijie Yang

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=132a8e29-3be7-422a-bc83-d6be00fac3e8@kernel.org \
    --to=krzk@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=kishon@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=linux-phy@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=quic_aiquny@quicinc.com \
    --cc=quic_tingweiz@quicinc.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