From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Qiang Yu" <qiang.yu@oss.qualcomm.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/6] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Add Kaanapali compatible
Date: Fri, 17 Oct 2025 07:00:32 +0200 [thread overview]
Message-ID: <61b7d2d6-6c53-4934-a2eb-8d92b50e0405@kernel.org> (raw)
In-Reply-To: <32a14a2e-f61e-422a-ae77-f60ea44581eb@kernel.org>
On 17/10/2025 06:47, Krzysztof Kozlowski wrote:
> On 15/10/2025 12:27, Qiang Yu wrote:
>> Document compatible for the QMP PCIe PHY on Kaanapali platform.
>>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
>
>
> Don't mix independent patches from different subsystems into one
> patchset. You only make it difficult for the maintainers.
>
> Really, really pay attention how your work should present itself to the
> maintainers.
>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
And please adjust and rebase on top of patch below:
20251017045919.34599-2-krzysztof.kozlowski@linaro.org
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-17 5:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 10:27 [PATCH v2 0/6] Add PCIe support for Kaanapali Qiang Yu
2025-10-15 10:27 ` [PATCH v2 1/6] dt-bindings: PCI: qcom,pcie-sm8550: Add Kaanapali compatible Qiang Yu
2025-10-17 4:46 ` Krzysztof Kozlowski
2025-10-15 10:27 ` [PATCH v2 2/6] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: " Qiang Yu
2025-10-17 4:47 ` Krzysztof Kozlowski
2025-10-17 5:00 ` Krzysztof Kozlowski [this message]
2025-10-18 5:08 ` Qiang Yu
2025-10-15 10:27 ` [PATCH v2 3/6] phy: qcom-qmp: qserdes-txrx: Add complete QMP PCIe PHY v8 register offsets Qiang Yu
2025-10-15 21:12 ` Dmitry Baryshkov
2025-10-15 10:27 ` [PATCH v2 4/6] phy: qcom-qmp: pcs-pcie: Add " Qiang Yu
2025-10-15 21:17 ` Dmitry Baryshkov
2025-10-15 10:27 ` [PATCH v2 5/6] phy: qcom-qmp: qserdes-com: Add some more " Qiang Yu
2025-10-15 10:27 ` [PATCH v2 6/6] phy: qcom: qmp-pcie: add QMP PCIe PHY tables for Kaanapali Qiang Yu
2025-10-16 0:05 ` Dmitry Baryshkov
2025-10-17 2:35 ` Qiang Yu
2025-10-19 7:14 ` (subset) [PATCH v2 0/6] Add PCIe support " Manivannan Sadhasivam
2025-10-27 13:21 ` Manivannan Sadhasivam
2025-10-27 13:22 ` Konrad Dybcio
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=61b7d2d6-6c53-4934-a2eb-8d92b50e0405@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=qiang.yu@oss.qualcomm.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