From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] scsi|phy: Add SM8450 UFS & Phy support
Date: Thu, 02 Dec 2021 21:58:10 -0500 [thread overview]
Message-ID: <yq135nawg3q.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20211201074456.3969849-1-vkoul@kernel.org> (Vinod Koul's message of "Wed, 1 Dec 2021 13:14:53 +0530")
Vinod,
> Add the binding documentation for ufs SM8450 compatible, phy
> compatible and SM8450 UFS QMP Phy support.
> .../devicetree/bindings/phy/qcom,qmp-phy.yaml | 1 +
> .../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 1 +
> drivers/phy/qualcomm/phy-qcom-qmp.c | 32 +++++++++++++++++++
No objections from me. However, these patches should go through the DT
and phy trees.
--
Martin K. Petersen Oracle Linux Engineering
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-12-03 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 7:44 [PATCH 0/3] scsi|phy: Add SM8450 UFS & Phy support Vinod Koul
2021-12-01 7:44 ` [PATCH 1/3] scsi: ufs: dt-bindings: Add SM8450 compatible strings Vinod Koul
2021-12-03 3:20 ` Bjorn Andersson
2021-12-13 19:02 ` Rob Herring
2021-12-01 7:44 ` [PATCH 2/3] dt-bindings: phy: qcom, qmp: Add SM8450 UFS phy compatible Vinod Koul
2021-12-03 3:19 ` [PATCH 2/3] dt-bindings: phy: qcom,qmp: " Bjorn Andersson
2021-12-01 7:44 ` [PATCH 3/3] phy: qcom-qmp: Add SM8450 UFS QMP Phy Vinod Koul
2021-12-03 3:20 ` Bjorn Andersson
2021-12-03 2:58 ` Martin K. Petersen [this message]
2021-12-03 17:42 ` [PATCH 0/3] scsi|phy: Add SM8450 UFS & Phy support Vinod Koul
2021-12-07 2:35 ` Martin K. Petersen
2021-12-07 11:59 ` Vinod Koul
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=yq135nawg3q.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--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).