From: Pradeep Pragallapati <pradeep.pragallapati@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH v2] arm64: dts: qcom: purwa-iot-evk: Enable UFS
Date: Mon, 23 Mar 2026 18:54:15 +0530 [thread overview]
Message-ID: <4ebca960-93bd-452b-a6e8-536223006991@oss.qualcomm.com> (raw)
In-Reply-To: <0794b29b-b999-47b8-a563-b29fa33a54f2@oss.qualcomm.com>
On 3/23/2026 6:25 PM, Konrad Dybcio wrote:
> On 3/23/26 1:47 PM, 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/
>
> This information should live below the --- line (in the ""cover letter""
> for this single-patch case), as we don't really care about that once it
> hits the git history
>
Agree. The statement below caused some confusion, which is why I added
it to the commit description.
If one patch depends on another patch in order for a change to be
complete, that is OK. Simply note “this patch depends on patch X” in
your patch description.
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Konrad
next prev parent reply other threads:[~2026-03-23 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 12:47 [PATCH v2] arm64: dts: qcom: purwa-iot-evk: Enable UFS Pradeep P V K
2026-03-23 12:55 ` Konrad Dybcio
2026-03-23 13:24 ` Pradeep Pragallapati [this message]
2026-03-30 16:01 ` 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=4ebca960-93bd-452b-a6e8-536223006991@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=konrad.dybcio@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