From: barnabas.czeman@mainlining.org
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: 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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 1/5] arm64: dts: qcom: msm8917-xiaomi-riva: Commonize for Redmi 4A and GO
Date: Mon, 09 Mar 2026 22:48:58 +0100 [thread overview]
Message-ID: <89ec6b4f9ff67a8ea035534da9b866fe@mainlining.org> (raw)
In-Reply-To: <ab66ac70-9c63-4dbc-9ec4-8dc5344fb045@oss.qualcomm.com>
On 2026-03-09 13:55, Konrad Dybcio wrote:
> On 3/5/26 6:28 PM, Barnabás Czémán wrote:
>> Redmi 5A is very similar for Redmi 4A (rolex) and Redmi GO (tiare),
>> it can be commonized for avoid unnecessary code duplications.
>>
>> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
>> ---
>
> Could you please try adding the following to your gitconfig:
>
> [diff]
> renameLimit = 999999
> algorithm = histogram # or 'copies'
> renames = copies
>
> and see if this generates a shorter diff?
It is inverting the diff there will be less change in
msm8917-xiaomi-riva-common.dtsi
and a lot of deletion in msm8917-xiaomi-riva.dts.
I can split the commit in that case rename will be shown properly but
riva devicetree
will be removed temporarily.
>
> Konrad
next prev parent reply other threads:[~2026-03-09 21:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:28 [PATCH 0/5] Commonize Redmi 5A for 4A and GO Barnabás Czémán
2026-03-05 17:28 ` [PATCH 1/5] arm64: dts: qcom: msm8917-xiaomi-riva: Commonize for Redmi " Barnabás Czémán
2026-03-06 8:21 ` Krzysztof Kozlowski
2026-03-09 12:55 ` Konrad Dybcio
2026-03-09 21:48 ` barnabas.czeman [this message]
2026-03-10 12:57 ` barnabas.czeman
2026-03-10 13:04 ` Konrad Dybcio
2026-03-10 13:11 ` barnabas.czeman
2026-03-10 13:21 ` Konrad Dybcio
2026-03-10 13:26 ` barnabas.czeman
2026-03-10 13:41 ` Konrad Dybcio
2026-03-05 17:28 ` [PATCH 2/5] dt-bindings: arm: qcom: Add Redmi 4A Barnabás Czémán
2026-03-09 10:57 ` Krzysztof Kozlowski
2026-03-09 12:50 ` Konrad Dybcio
2026-03-09 12:54 ` Krzysztof Kozlowski
2026-03-05 17:28 ` [PATCH 3/5] arm64: dts: " Barnabás Czémán
2026-03-09 12:52 ` Konrad Dybcio
2026-03-09 21:25 ` barnabas.czeman
2026-03-05 17:28 ` [PATCH 4/5] dt-bindings: arm: qcom: Add Redmi Go Barnabás Czémán
2026-03-06 8:21 ` Krzysztof Kozlowski
2026-03-06 8:29 ` Krzysztof Kozlowski
2026-03-05 17:28 ` [PATCH 5/5] arm64: dts: " Barnabás Czémán
2026-03-09 12:53 ` Konrad Dybcio
2026-03-09 21:19 ` barnabas.czeman
2026-03-09 21:36 ` barnabas.czeman
2026-03-10 12:31 ` Konrad Dybcio
2026-03-10 12:47 ` barnabas.czeman
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=89ec6b4f9ff67a8ea035534da9b866fe@mainlining.org \
--to=barnabas.czeman@mainlining.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=linux@mainlining.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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