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>,
Conor Dooley <conor+dt@kernel.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: [RESEND,PATCH 3/3] arm64: dts: qcom: sm8250-xiaomi-elish: remove redundant empty line
Date: Tue, 16 May 2023 15:27:34 +0800 [thread overview]
Message-ID: <ZGMwZiPI3eCGdoS8@Gentoo> (raw)
In-Reply-To: <95f257ae-0b9d-a002-7074-a476fbc5bc98@linaro.org>
On Tue, May 16, 2023 at 09:11:28AM +0200, Krzysztof Kozlowski wrote:
> On 16/05/2023 08:26, Jianhua Lu wrote:
> > Remove a redundant empty line introduced by
> > commit 51c4c2bd6f31 ("arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel")
>
> So you resent my patches just to add a comment? Not even as a dependency
> of something? Please, no.
Acked, I will split this patch to new series.
>
> >
> > Fixes: 51c4c2bd6f31 ("arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel")
>
> It's not a bug. Drop fixes tag.
Acked
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-05-16 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 6:26 [RESEND,PATCH 1/3] arm64: dts: qcom: sm8250-xiaomi-elish-boe: fix panel compatible Jianhua Lu
2023-05-16 6:26 ` [RESEND,PATCH 2/3] arm64: dts: qcom: sm8250-xiaomi-elish-csot: " Jianhua Lu
2023-05-16 6:26 ` [RESEND,PATCH 3/3] arm64: dts: qcom: sm8250-xiaomi-elish: remove redundant empty line Jianhua Lu
2023-05-16 7:11 ` Krzysztof Kozlowski
2023-05-16 7:27 ` Jianhua Lu [this message]
2023-05-16 7:01 ` [RESEND,PATCH 1/3] arm64: dts: qcom: sm8250-xiaomi-elish-boe: fix panel compatible Krzysztof Kozlowski
2023-05-16 7:23 ` Jianhua Lu
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=ZGMwZiPI3eCGdoS8@Gentoo \
--to=lujianhua000@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@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.