From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v5] memory: tegra210: Support interconnect framework
Date: Mon, 27 Oct 2025 18:32:27 +0100 [thread overview]
Message-ID: <491604f9-92c3-4b52-a17a-35d148b2c586@kernel.org> (raw)
In-Reply-To: <CALHNRZ9ZG2Vck4GB4an8-p-m39G2+YGffzOg630Ey6A6MHaCuA@mail.gmail.com>
On 27/10/2025 18:26, Aaron Kling wrote:
> On Mon, Oct 27, 2025 at 5:52 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 22/10/2025 05:10, Aaron Kling via B4 Relay wrote:
>>> From: Aaron Kling <webgeek1234@gmail.com>
>>>
>>> This makes mc and emc interconnect providers and allows for dynamic
>>> memory clock scaling.
>>>
>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>> ---
>>> Changes in v5:
>>> - Split series
>>> - Link to v4: https://lore.kernel.org/r/20250923-t210-actmon-v4-0-442d1eb6377c@gmail.com
>>>
>>
>>
>> Tried to apply... and see you did not run checkpatch.
>>
>> Please run scripts/checkpatch.pl on the patches and fix reported
>> warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
>> patches and (probably) fix more warnings. Some warnings can be ignored,
>> especially from --strict run, but the code here looks like it needs a
>> fix. Feel free to get in touch if the warning is not clear.
>
> I ran b4 prep --check, which runs checkpatch and that passes. And none
> of the kernel ci bots have complained. Normal checkpatch also passes.
> If I run strict, I get a warning like the following:
>
> #340: FILE: drivers/memory/tegra/tegra210-emc-core.c:2226:
> + if (!err) {
> [...]
> + } else if (err != -ENODEV)
> [...]
>
> The code flow should be correct here. Is this what you are referring
> to or are you getting an error/warning I'm not seeing?
Yeah, that is the warning I see. `b4 prep` does not run strict by
default. This would pop up when applying (git hooks would complain) and
after pushing (CI would complain).
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-27 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 3:10 Aaron Kling via B4 Relay
2025-10-27 10:52 ` Krzysztof Kozlowski
2025-10-27 17:26 ` Aaron Kling
2025-10-27 17:32 ` 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=491604f9-92c3-4b52-a17a-35d148b2c586@kernel.org \
--to=krzk@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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®