From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mahadevan P <mahadevan.p@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
jesszhan0024@gmail.com, quic_rajeevny@quicinc.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>,
Abhinav Kumar <abhinavk@quicinc.com>,
Abel Vesa <abel.vesa@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC/WIP 0/4] arm64: dts: qcom: sm8750: Enable display
Date: Thu, 30 Oct 2025 17:30:51 +0100 [thread overview]
Message-ID: <bfd59dc5-9503-4642-ba01-5f54c12c0175@kernel.org> (raw)
In-Reply-To: <58a658bb-7338-442f-ad8c-845b5fa5ce00@oss.qualcomm.com>
On 30/10/2025 13:21, Mahadevan P wrote:
>>
>>>
>>> Also, I’m curious to understand more about the DSI PHY PLL VCO rate issue that Jessica had narrowed down—could you please share some details?
>>>
>>> Lastly, I’d appreciate it if you could share the plan for merging these changes upstream. We’re aiming to enable display support on this target as part of our program.
>>
>> Please see Documentation/process/, I think it describes the process of
>> merging patches pretty well.
>
> Sorry for any confusion in my previous message. Could you please share
> when we might expect the next non-RFC version of this series,
> specifically for the DSI enablement patch? Alternatively, if there are
When dependencies get merged. The patchset cannot be merged and posting
something unmergeable, different than RFC, only clutters maintainers
mailboxes. Ask owners of dependencies about their status (as I said, I
stopped pinging for that)
> no immediate plans to post an updated version, would it be acceptable
> for us to take it forward and submit the subsequent non-RFC versions of
No, because the patch is ready. It is waiting on dependencies, so you
taking it would mean work is done twice. Plus you would not solve any
problem - still cannot submit it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-30 16:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 13:04 [PATCH RFC/WIP 0/4] arm64: dts: qcom: sm8750: Enable display Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 1/4] arm64: dts: qcom: sm8750: Add display (MDSS) with Display CC Krzysztof Kozlowski
2025-04-24 13:14 ` Krzysztof Kozlowski
2025-04-28 21:31 ` Konrad Dybcio
2025-04-29 23:07 ` Abhinav Kumar
2025-04-30 7:46 ` Konrad Dybcio
2025-05-05 6:49 ` Krzysztof Kozlowski
2025-05-05 7:25 ` Krzysztof Kozlowski
2025-05-03 5:51 ` Dmitry Baryshkov
2025-05-03 19:59 ` Abhinav Kumar
2025-05-03 21:01 ` Dmitry Baryshkov
2025-05-04 0:37 ` Abhinav Kumar
2025-10-29 7:40 ` Abel Vesa
2025-10-29 7:45 ` Krzysztof Kozlowski
2025-10-29 7:58 ` Abel Vesa
2025-04-24 13:04 ` [PATCH RFC/WIP 2/4] arm64: dts: qcom: sm8750-mtp: Enable display Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 3/4] arm64: dts: qcom: sm8750-mtp: Enable USB headset and Type-C altmode Krzysztof Kozlowski
2025-04-24 13:51 ` neil.armstrong
2025-04-24 14:39 ` Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 4/4] arm64: dts: qcom: sm8750-mtp: Enable DisplayPort over USB Krzysztof Kozlowski
2025-04-24 13:52 ` neil.armstrong
2025-04-25 19:34 ` [PATCH RFC/WIP 0/4] arm64: dts: qcom: sm8750: Enable display Dmitry Baryshkov
2025-04-25 19:54 ` Abhinav Kumar
2025-04-25 19:54 ` Krzysztof Kozlowski
2025-04-25 22:07 ` Dmitry Baryshkov
[not found] ` <32eb3b4f-b2c4-4895-8b48-ade319fd83de@oss.qualcomm.com>
2025-10-29 6:27 ` Krzysztof Kozlowski
2025-10-30 6:59 ` Jessica Zhang
2025-10-30 11:16 ` Dmitry Baryshkov
2025-10-30 12:21 ` Mahadevan P
2025-10-30 16:30 ` Krzysztof Kozlowski [this message]
2025-10-30 17:56 ` Dmitry Baryshkov
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=bfd59dc5-9503-4642-ba01-5f54c12c0175@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=abhinavk@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jesszhan0024@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahadevan.p@oss.qualcomm.com \
--cc=quic_rajeevny@quicinc.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