From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194
Date: Tue, 21 Oct 2025 21:50:02 +0200 [thread overview]
Message-ID: <da53e358-2d14-4dc7-ba88-79f8eceb2011@kernel.org> (raw)
In-Reply-To: <CALHNRZ9nXYRgjmpbR5KiQpsSf4hu4=qcgoh8F9_5b9yXF_5Btw@mail.gmail.com>
On 21/10/2025 21:19, Aaron Kling wrote:
> On Tue, Oct 21, 2025 at 2:11 PM Krzysztof Kozlowski <krzk@kernel.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@gmail.com>'
>> Grabbing thread from
>> lore.kernel.org/all/20251021-tegra186-icc-p2-v1-0-39d53bdc9aab@gmail.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
prev parent reply other threads:[~2025-10-21 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:29 [PATCH 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194 Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 18:29 ` [PATCH 1/5] dt-bindings: memory: tegra186-mc: Add dummy client IDs for Tegra186 Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 18:29 ` [PATCH 2/5] dt-bindings: memory: tegra194-mc: Add dummy client IDs for Tegra194 Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 18:29 ` [PATCH 3/5] memory: tegra186-emc: Support non-bpmp icc scaling Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 18:29 ` [PATCH 4/5] memory: tegra186: Support " Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 18:29 ` [PATCH 5/5] memory: tegra194: " Aaron Kling
2025-10-21 18:29 ` Aaron Kling via B4 Relay
2025-10-21 19:11 ` [PATCH 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194 Krzysztof Kozlowski
2025-10-21 19:19 ` Aaron Kling
2025-10-21 19:50 ` Krzysztof Kozlowski [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=da53e358-2d14-4dc7-ba88-79f8eceb2011@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.com \
/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.