From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jianhua Lu <lujianhua000@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] arm64: dts: qcom: Split elish dts into common dtsi and elish-boe dts
Date: Thu, 23 Mar 2023 07:52:05 +0100 [thread overview]
Message-ID: <ea980e5c-3dc8-0fd6-8635-8f58a0745ac5@linaro.org> (raw)
In-Reply-To: <20230323005925.23179-1-lujianhua000@gmail.com>
On 23/03/2023 01:59, Jianhua Lu wrote:
> There are two panel variants of xiaomi-elish, BOE and CSOT panels.
> In order to support both panels, so split elish dts into common dtsi
> and elish-boe dts.
>
> Signed-off-by: Jianhua Lu <lujianhua000@gmail.com>
> ---
> Changes in v2:
> - Remove sm8250-xiaomi-elish.dtb to avoid build failure.
>
> Changes in v3:
> - squash patch[3/4]
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-23 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 0:59 [PATCH v3 1/3] arm64: dts: qcom: Split elish dts into common dtsi and elish-boe dts Jianhua Lu
2023-03-23 0:59 ` [PATCH v3 2/3] arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel Jianhua Lu
2023-03-23 16:16 ` Konrad Dybcio
2023-04-08 13:04 ` Krzysztof Kozlowski
2023-04-08 13:33 ` Jianhua Lu
2023-03-23 0:59 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250-xiaomi-elish-csot: Add Xiaomi Mi Pad 5 Pro CSOT variant Jianhua Lu
2023-03-23 6:52 ` Krzysztof Kozlowski [this message]
2023-04-07 18:51 ` (subset) [PATCH v3 1/3] arm64: dts: qcom: Split elish dts into common dtsi and elish-boe dts 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=ea980e5c-3dc8-0fd6-8635-8f58a0745ac5@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lujianhua000@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).