From: Bjorn Helgaas <helgaas@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Johan Hovold" <johan@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 4/7] phy: qcom-qmp-pcie: split and rename the sm8450 gen3 PHY config tables
Date: Sun, 30 Oct 2022 07:25:25 -0500 [thread overview]
Message-ID: <20221030122525.GA1022832@bhelgaas> (raw)
In-Reply-To: <20221029211312.929862-5-dmitry.baryshkov@linaro.org>
On Sun, Oct 30, 2022 at 12:13:09AM +0300, Dmitry Baryshkov wrote:
> SM8350 PHY config tables are mostly the same as SM8450 gen3 PHY config
> tables. Split these tables to be used by SM8350 config. Following this
> split rename generic tables to remove x1 suffix.
Commit logs that say "Following this ..." always make me ask whether
this could or should be split into two patches, one that is a trivial
rename that's easier to review.
But I guess this is a phy patch that Lorenzo will look for somebody
else to ack :)
Bjorn
next prev parent reply other threads:[~2022-10-30 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 21:13 [PATCH v1 0/7] PCI/phy: Add support for PCI on sm8350 platform Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 1/7] dt-bindings: PCI: qcom: Add sm8350 to bindings Dmitry Baryshkov
2022-10-31 21:40 ` Rob Herring
2022-10-31 21:47 ` Dmitry Baryshkov
2022-11-01 17:22 ` Rob Herring
2022-11-10 10:02 ` Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 2/7] dt-bindings: phy: qcom,qmp-pcie: add sm8350 bindings Dmitry Baryshkov
2022-10-31 21:41 ` Rob Herring
2022-10-29 21:13 ` [PATCH v1 3/7] PCI: qcom: Add support for SM8350 Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 4/7] phy: qcom-qmp-pcie: split and rename the sm8450 gen3 PHY config tables Dmitry Baryshkov
2022-10-30 12:25 ` Bjorn Helgaas [this message]
2022-10-30 14:05 ` Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 5/7] phy: qcom-qmp-pcie: add support for sm8350 platform Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 6/7] arm64: dts: qcom: sm8350: add PCIe devices Dmitry Baryshkov
2022-10-29 21:13 ` [PATCH v1 7/7] arm64: dts: qcom: sm8350-hdk: enable " Dmitry Baryshkov
2022-10-30 12:23 ` [PATCH v1 0/7] PCI/phy: Add support for PCI on sm8350 platform Bjorn Helgaas
2022-10-30 14:26 ` Dmitry Baryshkov
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=20221030122525.GA1022832@bhelgaas \
--to=helgaas@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).