From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gopi Botlagunta <venkata.botlagunta@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, venkata.valluru@oss.qualcomm.com,
jessica.zhang@oss.qualcomm.com
Subject: Re: [PATCH] arm64: dts: qcom: lemans-evk: Enable mdss1 display Port
Date: Thu, 19 Feb 2026 15:24:24 +0100 [thread overview]
Message-ID: <d54f4b17-a137-494b-b103-2734987c4f14@kernel.org> (raw)
In-Reply-To: <20260219-enable-edp2-3-lemans-evk-mezzanine-v1-1-969316806538@oss.qualcomm.com>
On 19/02/2026 14:36, Gopi Botlagunta wrote:
> This change enables DP controllers, DPTX0 and DPTX1 alongside
Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v6.16/source/Documentation/process/submitting-patches.rst#L94
>
> ---
> base-commit: 1a0829927afbfe654c632eb2e779fa32df825b06
> change-id: 20260219-enable-edp2-3-lemans-evk-mezzanine-1bef9932ee6d
> prerequisite-message-id: 20260203193848.123307-2-umang.chheda@oss.qualcomm.com
> prerequisite-patch-id: baf07fce333b86c35c3d4cefbba5800a519952a3
> prerequisite-message-id: 20260217071420.2240380-1-mkuntuma@qti.qualcomm.com
> prerequisite-patch-id: 74a76fd6a1129cdbbd32d91d2a119d693dba78a7
> prerequisite-patch-id: f4a858f7e707c8e330daf2ea1f4da58b4da00f05
>
Why do you have so many dependencies? Why isn't this merged there?
Was this patch tested (see internal testing guideline) prior to posting?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-19 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 13:36 [PATCH] arm64: dts: qcom: lemans-evk: Enable mdss1 display Port Gopi Botlagunta
2026-02-19 13:41 ` Konrad Dybcio
2026-03-27 6:51 ` Gopi Botlagunta
2026-02-19 14:24 ` Krzysztof Kozlowski [this message]
2026-03-27 7:08 ` Gopi Botlagunta
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=d54f4b17-a137-494b-b103-2734987c4f14@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jessica.zhang@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=robh@kernel.org \
--cc=venkata.botlagunta@oss.qualcomm.com \
--cc=venkata.valluru@oss.qualcomm.com \
/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