From: Jianhua Lu <lujianhua000@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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>,
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 1/4] arm64: dts: qcom: move elish dts to common dtsi
Date: Thu, 23 Mar 2023 00:47:18 +0800 [thread overview]
Message-ID: <ZBsxFh2qH6hv2Wo1@Gentoo> (raw)
In-Reply-To: <2cb5fca2-56bc-c706-912b-2b8eaf7b3b94@linaro.org>
On Wed, Mar 22, 2023 at 05:32:06PM +0100, Krzysztof Kozlowski wrote:
> On 22/03/2023 16:03, Jianhua Lu wrote:
> > There are two panel variants of xiaomi-elish, BOE and CSOT panel.
> > In order to support both panels, so move elish dts to common dtsi.
> >
> > Signed-off-by: Jianhua Lu <lujianhua000@gmail.com>
> > ---
> > ...m8250-xiaomi-elish.dts => sm8250-xiaomi-elish-common.dtsi} | 4 ----
>
> This breaks the build.
Thanks for spotting it. I will fix it in v2.
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2023-03-22 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:03 [PATCH 1/4] arm64: dts: qcom: move elish dts to common dtsi Jianhua Lu
2023-03-22 15:03 ` [PATCH 2/4] arm64: dts: qcom: sm8250-xiaomi-elish: add mdss and dsi node Jianhua Lu
2023-03-22 15:03 ` [PATCH 3/4] arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add Xiaomi Mi Pad 5 Pro BOE variant Jianhua Lu
2023-03-23 0:34 ` kernel test robot
2023-03-22 15:03 ` [PATCH 4/4] arm64: dts: qcom: sm8250-xiaomi-elish-csot: Add Xiaomi Mi Pad 5 Pro CSOT variant Jianhua Lu
2023-03-22 16:32 ` [PATCH 1/4] arm64: dts: qcom: move elish dts to common dtsi Krzysztof Kozlowski
2023-03-22 16:47 ` Jianhua Lu [this message]
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=ZBsxFh2qH6hv2Wo1@Gentoo \
--to=lujianhua000@gmail.com \
--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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.