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 v3 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194
Date: Mon, 27 Oct 2025 19:42:24 +0100 [thread overview]
Message-ID: <2491c23e-430d-4f1b-827e-1298996fce59@kernel.org> (raw)
In-Reply-To: <CALHNRZ-6Wp1k9zWg=B5xSt7n_9Fj9XchBq7qniKZtKHkHVouZg@mail.gmail.com>
On 27/10/2025 18:54, Aaron Kling wrote:
> On Mon, Oct 27, 2025 at 5:49 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 22/10/2025 03:09, 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.
>>>
>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>
>>
>> Does not apply, please check, rebase and resend.
>>
>> Patch failed at 0003 memory: tegra186-emc: Support non-bpmp icc scaling
>> error: patch failed: drivers/memory/tegra/tegra186-emc.c:217
>> error: drivers/memory/tegra/tegra186-emc.c: patch does not apply
>
> It applies on v6.18-rc3, but not next. Your cleanup series caused the
> conflict. I'll rebase on next-20251027 and resend.
Patches should apply on maintainer's for-next branches, not mainline.
My cleanup series were applied two weeks ago, so week or more before you
sent it.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-27 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 1:09 Aaron Kling via B4 Relay
2025-10-22 1:09 ` [PATCH v3 1/5] dt-bindings: memory: tegra186-mc: Add dummy client IDs for Tegra186 Aaron Kling via B4 Relay
2025-10-22 1:09 ` [PATCH v3 2/5] dt-bindings: memory: tegra194-mc: Add dummy client IDs for Tegra194 Aaron Kling via B4 Relay
2025-10-22 1:09 ` [PATCH v3 3/5] memory: tegra186-emc: Support non-bpmp icc scaling Aaron Kling via B4 Relay
2025-10-22 1:09 ` [PATCH v3 4/5] memory: tegra186: Support " Aaron Kling via B4 Relay
2025-10-22 1:09 ` [PATCH v3 5/5] memory: tegra194: " Aaron Kling via B4 Relay
2025-10-27 10:49 ` [PATCH v3 0/5] memory: tegra: Support EMC dfs on Tegra186/Tegra194 Krzysztof Kozlowski
2025-10-27 17:54 ` Aaron Kling
2025-10-27 18:42 ` 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=2491c23e-430d-4f1b-827e-1298996fce59@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®