Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Yongxing Mou <quic_yongmou@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] arm64: dts: qcom: qcs8300: add display dt nodes for MDSS, DPU, DisplayPort and eDP PHY
Date: Wed, 12 Feb 2025 09:36:57 +0100	[thread overview]
Message-ID: <ee16cd97-a2fe-48ec-bb9c-e9d806da7615@kernel.org> (raw)
In-Reply-To: <7778b91c-aa94-4010-89bc-5e86f78ae275@oss.qualcomm.com>

On 03/02/2025 14:53, Konrad Dybcio wrote:
> On 3.02.2025 2:43 PM, Konrad Dybcio wrote:
>> On 14.01.2025 7:59 AM, Yongxing Mou wrote:
>>> Add devicetree changes to enable MDSS display-subsystem,
>>> display-controller(DPU), DisplayPort controller and eDP PHY for
>>> Qualcomm QCS8300 platform.
>>>
>>> Signed-off-by: Yongxing Mou <quic_yongmou@quicinc.com>
>>> ---
>>
>> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> 
> Wrong copypasta, please use this one instead:
> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Author said it is wrong few days ago, so you can drop it.

Best regards,
Krzysztof

  reply	other threads:[~2025-02-12  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  6:59 [PATCH v3 0/2] Enable DPU and Display Port for Qualcomm QCS8300-ride platform Yongxing Mou
2025-01-14  6:59 ` [PATCH v3 1/2] arm64: dts: qcom: qcs8300: add display dt nodes for MDSS, DPU, DisplayPort and eDP PHY Yongxing Mou
2025-02-03 13:43   ` Konrad Dybcio
2025-02-03 13:53     ` Konrad Dybcio
2025-02-12  8:36       ` Krzysztof Kozlowski [this message]
2025-02-12  8:36   ` Krzysztof Kozlowski
2025-01-14  6:59 ` [PATCH v3 2/2] arm64: dts: qcom: qcs8300-ride: Enable Display Port Yongxing Mou

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=ee16cd97-a2fe-48ec-bb9c-e9d806da7615@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=quic_yongmou@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