From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Pradeep P V K <pradeep.pragallapati@oss.qualcomm.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
martin.petersen@oracle.com, andersson@kernel.org,
konradybcio@kernel.org, taniya.das@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com,
manivannan.sadhasivam@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH V5 0/3] Add UFS support for x1e80100 SoC
Date: Tue, 24 Feb 2026 14:40:06 -0500 [thread overview]
Message-ID: <yq1seaq6ifd.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260211132926.3716716-1-pradeep.pragallapati@oss.qualcomm.com> (Pradeep P. V. K.'s message of "Wed, 11 Feb 2026 18:59:23 +0530")
Pradeep,
> Add UFSPHY, UFSHC compatible binding names and UFS devicetree
> enablement changes for Qualcomm x1e80100 SoC.
Applied to 7.1/scsi-staging. Please validate conflict resolution in
qcom,sc7180-ufshc.yaml, thanks!
--
Martin K. Petersen
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-02-24 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 13:29 [PATCH V5 0/3] Add UFS support for x1e80100 SoC Pradeep P V K
2026-02-11 13:29 ` [PATCH V5 1/3] dt-bindings: ufs: qcom,sc7180-ufshc: Add UFSHC compatible for x1e80100 Pradeep P V K
2026-02-11 13:29 ` [PATCH V5 2/3] arm64: dts: qcom: hamoa: Add UFS nodes for x1e80100 SoC Pradeep P V K
2026-02-11 13:29 ` [PATCH V5 3/3] arm64: dts: qcom: hamoa-iot-evk: Enable UFS Pradeep P V K
2026-02-24 19:40 ` Martin K. Petersen [this message]
2026-02-25 8:58 ` [PATCH V5 0/3] Add UFS support for x1e80100 SoC Krzysztof Kozlowski
2026-03-11 2:06 ` Martin K. Petersen
2026-03-23 14:38 ` (subset) " Bjorn Andersson
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=yq1seaq6ifd.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=pradeep.pragallapati@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=taniya.das@oss.qualcomm.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