From: Dragan Simic <dsimic@manjaro.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: Alexey Charkov <alchark@gmail.com>,
linux-rockchip@lists.infradead.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, quentin.schulz@cherry.de,
wens@kernel.org, daniel.lezcano@linaro.org,
krzysztof.kozlowski+dt@linaro.org, viresh.kumar@linaro.org
Subject: Re: [RFC PATCH] arm64: dts: rockchip: Make preparations for per-RK3588-variant OPPs
Date: Fri, 31 May 2024 04:45:28 +0200 [thread overview]
Message-ID: <06452ce330f0a712e4d765475c6cbc8b@manjaro.org> (raw)
In-Reply-To: <511137f077495007f467d5927f42f85d@manjaro.org>
On 2024-05-29 13:33, Dragan Simic wrote:
> On 2024-05-29 13:09, Diederik de Haas wrote:
>> On Wednesday, 29 May 2024 11:57:45 CEST Alexey Charkov wrote:
[...]
>>> > arch/arm64/boot/dts/rockchip/rk3588.dtsi | 414 +--
>>> > arch/arm64/boot/dts/rockchip/rk3588j.dtsi | 6 +-
>>> > arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 2671 +----------------
>>>
>>> Rename detection didn't do a particularly great job here - wonder if
>>> we can do anything about it to minimize the patch size and ensure
>>> that
>>> the change history is preserved for git blame...
>>
>> +1
>> The diff does look awfully big for a rename operation, which was
>> supposed to
>> (also only) "modify ... a bit".
>
> I also don't like the size of the patch. I just tried playing with
> specifying different values for the --find-renames and --find-copies
> options, but with no good results. I'll have a look into the Git
> source later, to see what's actually going on with those options.
Yay, --break-rewrites makes the diff extremely compact. :) [1]
[1]
https://git-scm.com/docs/git-diff#Documentation/git-diff.txt--Bltngtltmgt
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2024-05-31 2:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 2:13 [RFC PATCH] arm64: dts: rockchip: Make preparations for per-RK3588-variant OPPs Dragan Simic
2024-05-29 9:57 ` Alexey Charkov
2024-05-29 10:45 ` Dragan Simic
2024-05-29 12:04 ` Alexey Charkov
2024-05-29 12:22 ` Dragan Simic
2024-05-29 14:05 ` Alexey Charkov
2024-05-30 19:31 ` Dragan Simic
2024-05-31 11:27 ` Jonas Karlman
2024-05-31 11:44 ` Alexey Charkov
2024-05-31 23:32 ` Jonas Karlman
2024-05-31 21:24 ` Dragan Simic
2024-05-31 23:15 ` Jonas Karlman
2024-05-31 23:39 ` Dragan Simic
2024-06-04 20:48 ` Dragan Simic
2024-05-29 11:09 ` Diederik de Haas
2024-05-29 11:33 ` Dragan Simic
2024-05-31 2:45 ` Dragan Simic [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=06452ce330f0a712e4d765475c6cbc8b@manjaro.org \
--to=dsimic@manjaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wens@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