From: Vinod Koul <vkoul@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH v3 00/11] phy: qcom-qmp-ufs: convert to newer style of bindings
Date: Wed, 12 Jul 2023 10:31:54 +0530 [thread overview]
Message-ID: <168913811417.211971.4997836227104181246.b4-ty@kernel.org> (raw)
In-Reply-To: <20230523140622.265692-1-dmitry.baryshkov@linaro.org>
On Tue, 23 May 2023 17:06:11 +0300, Dmitry Baryshkov wrote:
> Reviewing several patchsets for newer platforms made me understand that
> having two styles of QMP PHY bindings causes confusion. Despite binding
> documents having notes telling that old bindings should be used for
> older platforms, it is too easy to attempt adding new platform with
> older QMP PHY binding. Thus let's have just a single documented style of
> bindings.
>
> [...]
Applied, thanks!
[01/11] dt-bindings: phy: migrate QMP UFS PHY bindings to qcom,sc8280xp-qmp-ufs-phy.yaml
commit: cd296e74242918f91bb86da0c67d8456338cbb16
[02/11] phy: qcom-qmp-ufs: populate offsets configuration
commit: e2d9dbc01cb305af625c6db83c451645eef64470
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2023-07-12 5:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 14:06 [PATCH v3 00/11] phy: qcom-qmp-ufs: convert to newer style of bindings Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 01/11] dt-bindings: phy: migrate QMP UFS PHY bindings to qcom,sc8280xp-qmp-ufs-phy.yaml Dmitry Baryshkov
2023-06-25 15:57 ` Krzysztof Kozlowski
2023-07-11 4:59 ` Vinod Koul
2023-05-23 14:06 ` [PATCH v3 02/11] phy: qcom-qmp-ufs: populate offsets configuration Dmitry Baryshkov
2023-06-13 22:15 ` Bjorn Andersson
2023-05-23 14:06 ` [PATCH v3 03/11] arm64: dts: qcom: msm8996: switch UFS QMP PHY to new style of bindings Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 04/11] arm64: dts: qcom: msm8998: " Dmitry Baryshkov
2023-05-23 17:34 ` Konrad Dybcio
2023-05-23 14:06 ` [PATCH v3 05/11] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2023-05-23 17:34 ` Konrad Dybcio
2023-05-23 14:06 ` [PATCH v3 06/11] arm64: dts: qcom: sm6115: " Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 07/11] arm64: dts: qcom: sm6350: " Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 08/11] arm64: dts: qcom: sm8150: " Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 09/11] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 10/11] arm64: dts: qcom: sm8350: " Dmitry Baryshkov
2023-05-23 14:06 ` [PATCH v3 11/11] arm64: dts: qcom: sm8450: " Dmitry Baryshkov
2023-07-12 5:01 ` Vinod Koul [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=168913811417.211971.4997836227104181246.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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