linux-kernel - Re: [PATCH 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <da53e358-2d14-4dc7-ba88-79f8eceb2011@kernel.org>
Date: Tue, 21 Oct 2025 21:50:02 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Aaron Kling <webgeek1234@...il.com>
Cc: Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Thierry Reding <thierry.reding@...il.com>,
 Jonathan Hunter <jonathanh@...dia.com>, linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194

On 21/10/2025 21:19, Aaron Kling wrote:
> On Tue, Oct 21, 2025 at 2:11 PM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>
>> On 21/10/2025 20:29, Aaron Kling via B4 Relay wrote:
>>> This series borrows the concept used on Tegra234 to scale EMC based on
>>> CPU frequency and applies it to Tegra186 and Tegra194. Except that the
>>> bpmp on those archs does not support bandwidth manager, so the scaling
>>> iteself is handled similar to how Tegra124 currently works.
>>>
>>> This was originally part of a larger series [0], but it was requested to
>>> be split into smaller series.
>>>
>>> [0] https://lore.kernel.org/r/20250909-tegra186-icc-v2-0-09413724e781@gmail.com
>>
>> Please keep correct versioning and changelog in the future. Try yourself:
>>
>> b4 diff '<20251021-tegra186-icc-p2-v1-0-39d53bdc9aab@...il.com>'
>> Grabbing thread from
>> lore.kernel.org/all/20251021-tegra186-icc-p2-v1-0-39d53bdc9aab@...il.com/t.mbox.gz
>> ---
>> Analyzing 6 messages in the thread
>> Could not find lower series to compare against.
>>
>> I think I emphasized last time how important is to make it readable and
>> easy for maintainers.
> 
> You said to split it, which I don't see how that means anything other
> than 'make new series'. How am I supposed to keep versioning when I

New series with old changelog! Why splitting means that entire old
discussions, old tags, old reviews, everything should be discarded?

> had to make three entirely new series?

I do not see where is the problem - it is trivial. If you use git, you
just keep numbering. If you use b4, you just force-revision n+1.

Best regards,
Krzysztof