From: Pradeep Pragallapati <pradeep.pragallapati@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, mani@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH 0/1] Enable UFS for purwa-iot-evk
Date: Mon, 23 Mar 2026 18:06:02 +0530 [thread overview]
Message-ID: <42b80288-5a3d-454a-bc1b-c80bebe2dd03@oss.qualcomm.com> (raw)
In-Reply-To: <lmmlmpu7h6rm5ddi6aaspayhaibeyr274xjqqquaxtrovusnps@5p22xw3vcbnk>
On 3/17/2026 8:17 PM, Dmitry Baryshkov wrote:
> On Tue, Mar 17, 2026 at 12:43:10PM +0530, Pradeep P V K wrote:
>> Enable UFS for PURWA-IOT-EVK board.
>>
>> This patch depends on [PATCH V5 2/3] arm64: dts: qcom: hamoa: Add UFS
>> nodes for x1e80100 SoC
>> https://lore.kernel.org/all/20260211132926.3716716-3-pradeep.pragallapati@oss.qualcomm.com/
>
> No need for the cover letter for 1-patch series. Please switch to the b4
> tool.
>
Noted. Sure will use b4 going forward.
>>
>> Pradeep P V K (1):
>> arm64: dts: qcom: purwa-iot-evk: Enable UFS
>>
>> arch/arm64/boot/dts/qcom/purwa-iot-evk.dts | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>>
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2026-03-23 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 7:13 Pradeep P V K
2026-03-17 7:13 ` [PATCH 1/1] arm64: dts: qcom: purwa-iot-evk: Enable UFS Pradeep P V K
2026-03-17 7:33 ` Manivannan Sadhasivam
2026-03-17 11:56 ` Pradeep Pragallapati
2026-03-17 14:47 ` [PATCH 0/1] Enable UFS for purwa-iot-evk Dmitry Baryshkov
2026-03-23 12:36 ` Pradeep Pragallapati [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=42b80288-5a3d-454a-bc1b-c80bebe2dd03@oss.qualcomm.com \
--to=pradeep.pragallapati@oss.qualcomm.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=mani@kernel.org \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=robh@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
all inboxes | Powered by JetHome®