From: Bjorn Andersson <andersson@kernel.org>
To: shawn.guo@linaro.org, kw@linux.com, linux-pci@vger.kernel.org,
lpieralisi@kernel.org, konrad.dybcio@linaro.org,
bhelgaas@google.com, robh@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
Robert Marko <robimarko@gmail.com>,
linux-arm-msm@vger.kernel.org, agross@kernel.org,
svarbanov@mm-sol.com, mani@kernel.org
Subject: Re: (subset) [PATCH v2 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY
Date: Wed, 18 Jan 2023 22:54:00 -0600 [thread overview]
Message-ID: <167410403679.3048186.3473019994896236828.b4-ty@kernel.org> (raw)
In-Reply-To: <20230113164449.906002-1-robimarko@gmail.com>
On Fri, 13 Jan 2023 17:44:41 +0100, Robert Marko wrote:
> Serdes register space sizes are incorrect, update them to match the
> actual sizes from downstream QCA 5.4 kernel.
>
>
Applied, thanks!
[1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY
commit: 100d9c94ccf15b02742c326cd04f422ab729153b
[2/9] arm64: dts: qcom: ipq8074: fix Gen3 PCIe QMP PHY
commit: 7ba33591b45f9d547a317e42f1c2acd19c925eb6
[3/9] arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges
commit: 2055cb7dccea16bafa3adf9c5e3216949512c34a
[4/9] arm64: dts: qcom: ipq8074: set Gen2 PCIe pcie max-link-speed
commit: b60590314828e3da670bed94129f4ebc02b87548
[8/9] arm64: dts: qcom: ipq8074: fix Gen3 PCIe node
commit: 3e83a9c41ab0244a45a4a2800b9adb8de0d15f82
[9/9] arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names
commit: 0e8b90c0256cf9c9589e2cee517dedc987a34355
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-01-19 5:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 16:44 [PATCH v2 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY Robert Marko
2023-01-13 16:44 ` [PATCH v2 2/9] arm64: dts: qcom: ipq8074: fix Gen3 " Robert Marko
2023-01-13 16:44 ` [PATCH v2 3/9] arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges Robert Marko
2023-01-13 16:44 ` [PATCH v2 4/9] arm64: dts: qcom: ipq8074: set Gen2 PCIe pcie max-link-speed Robert Marko
2023-01-13 16:44 ` [PATCH v2 5/9] dt-bindings: PCI: qcom: alphabetically sort compatibles Robert Marko
2023-01-13 16:44 ` [PATCH v2 6/9] dt-bindings: PCI: qcom: document IPQ8074 Gen3 port Robert Marko
2023-01-13 16:44 ` [PATCH v2 7/9] PCI: qcom: Add support for " Robert Marko
2023-01-13 16:44 ` [PATCH v2 8/9] arm64: dts: qcom: ipq8074: fix Gen3 PCIe node Robert Marko
2023-01-30 17:11 ` Arnd Bergmann
2023-02-02 9:16 ` Robert Marko
2023-02-02 9:42 ` Arnd Bergmann
2023-02-28 13:20 ` Manivannan Sadhasivam
2023-03-01 10:57 ` Robert Marko
2023-01-13 16:44 ` [PATCH v2 9/9] arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names Robert Marko
2023-01-16 9:14 ` (subset) [PATCH v2 1/9] arm64: dts: qcom: ipq8074: fix Gen2 PCIe QMP PHY Lorenzo Pieralisi
2023-01-19 4:54 ` Bjorn Andersson [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=167410403679.3048186.3473019994896236828.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=svarbanov@mm-sol.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