From: Krzysztof Kozlowski <krzk@kernel.org>
To: George Moussalem <george.moussalem@outlook.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-phy@lists.infradead.org,
andersson@kernel.org, bhelgaas@google.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, dmitry.baryshkov@linaro.org,
kishon@kernel.org, konradybcio@kernel.org, krzk+dt@kernel.org,
kw@linux.com, lpieralisi@kernel.org,
manivannan.sadhasivam@linaro.org, p.zabel@pengutronix.de,
quic_nsekar@quicinc.com, robh@kernel.org, robimarko@gmail.com,
vkoul@kernel.org
Cc: quic_srichara@quicinc.com
Subject: Re: [PATCH v3 0/6] Enable IPQ5018 PCI support
Date: Thu, 6 Mar 2025 08:18:19 +0100 [thread overview]
Message-ID: <b118bc5a-9f5c-476d-8af6-31e793ec5479@kernel.org> (raw)
In-Reply-To: <DS7PR19MB8883484545BE6AE9E12B5AF69DCB2@DS7PR19MB8883.namprd19.prod.outlook.com>
On 05/03/2025 17:59, George Moussalem wrote:
>> On 05/03/2025 14:41, George Moussalem wrote:
>>> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>> Not correct From. Cover letter should be written by you.
> Noted. I thought I'd keep the original author included and added my v3 changes which you rightfully pointed out should have been v4 instead.
> Will remove in next version.
>>
>>> This patch series adds the relevant phy and controller
>>> DT configurations for enabling PCI gen2 support
>>> on IPQ5018. IPQ5018 has two phys and two controllers,
>>> one dual-lane and one single-lane.
>>>
>>> Last patch series (v2) submitted dates back to August 27, 2024.
>>> As I've worked to add IPQ5018 platform support in OpenWrt, I'm
>>> continuing the efforts to add Linux kernel support.
>>>
>>> v3:
>>> *) Depends on: https://patchwork.kernel.org/project/linux-arm-msm/cover/20250220094251.230936-1-quic_varada@quicinc.com/
>>
>> Wasn't this applied, so why is it still a dependency?
> I explicitly added it as ipq5332 has not made it to the master branch yet. Should I remove?
If you treat something not yet released as dependency, then please stop
sending so many versions because nothing here can be applied for this cycle.
Why is this a dependency?
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-03-06 7:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250305134239.2236590-1-george.moussalem@outlook.com>
2025-03-05 13:41 ` [PATCH v3 0/6] Enable IPQ5018 PCI support George Moussalem
2025-03-05 16:49 ` Krzysztof Kozlowski
2025-03-05 16:59 ` George Moussalem
2025-03-06 7:18 ` Krzysztof Kozlowski [this message]
2025-03-05 13:41 ` [PATCH v3 1/6] dt-bindings: phy: qcom: uniphy-pcie: Add ipq5018 compatible George Moussalem
2025-03-05 13:41 ` [PATCH v3 2/6] phy: qualcomm: qcom-uniphy-pcie 28LP add support for IPQ5018 George Moussalem
2025-03-05 20:39 ` Dmitry Baryshkov
2025-03-08 14:25 ` Konrad Dybcio
2025-03-08 15:29 ` Dmitry Baryshkov
2025-03-05 13:41 ` [PATCH v3 3/6] dt-bindings: PCI: qcom: Add IPQ5018 SoC George Moussalem
2025-03-05 15:51 ` Krzysztof Kozlowski
2025-03-05 16:41 ` George Moussalem
2025-03-05 16:45 ` Krzysztof Kozlowski
2025-03-06 7:24 ` Krzysztof Kozlowski
2025-03-13 5:55 ` George Moussalem
2025-03-05 13:41 ` [PATCH v3 4/6] PCI: qcom: Add support for IPQ5018 George Moussalem
2025-03-13 6:00 ` Manivannan Sadhasivam
2025-03-05 13:41 ` [PATCH v3 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes George Moussalem
2025-03-08 15:08 ` Konrad Dybcio
2025-03-13 6:09 ` George Moussalem
2025-03-18 7:17 ` Manivannan Sadhasivam
2025-03-18 9:41 ` George Moussalem
2025-03-24 7:33 ` Manivannan Sadhasivam
2025-03-05 13:41 ` [PATCH v3 6/6] arm64: dts: qcom: ipq5018: Enable PCIe George Moussalem
2025-03-05 13:41 [PATCH v3 0/6] Enable IPQ5018 PCI support George Moussalem
2025-03-05 16:47 ` Krzysztof Kozlowski
2025-03-05 17:54 ` George Moussalem
-- strict thread matches above, loose matches on Subject: below --
2024-08-30 8:11 [PATCH V3 " Sricharan R
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=b118bc5a-9f5c-476d-8af6-31e793ec5479@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=dmitry.baryshkov@linaro.org \
--cc=george.moussalem@outlook.com \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--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=manivannan.sadhasivam@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_nsekar@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--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