From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"biju.das.au" <biju.das.au@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] memory: renesas-rpc-if: Add missing static keyword
Date: Thu, 8 May 2025 11:10:51 +0200 [thread overview]
Message-ID: <ff5f4f3c-75b8-46a8-83e2-b1d1533371fd@kernel.org> (raw)
In-Reply-To: <TY3PR01MB11346F3A3F4C3C79F462F1D6F868BA@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 08/05/2025 11:05, Biju Das wrote:
> Hi Krzysztof,
>
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: 08 May 2025 09:57
>> Subject: Re: [PATCH] memory: renesas-rpc-if: Add missing static keyword
>>
>> On 07/05/2025 18:21, Biju Das wrote:
>>> Fix the below sparse warnings:
>>> symbol 'rpcif_impl' was not declared. Should it be static?
>>> symbol 'xspi_impl' was not declared. Should it be static?
>>
>>
>> Did you test now your code with sparse and smatch? Otherwise I will wait for more reports.
>
> Yes, I tested with the instructions in [1] and the patch fixes the above issues.
>
I meant other issues. So you did not test with smatch? That's your task
and you should not rely on the community to provide such tests/checks
instead.
Please run standard kernel tools for static analysis, like coccinelle,
smatch and sparse, and fix reported warnings. Also please check for
warnings when building with W=1 for gcc and clang. Most of these
commands (checks or W=1 build) can build specific targets, like some
directory, to narrow the scope to only your code. The code here looks
like it needs a fix. Feel free to get in touch if the warning is not clear.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-08 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 16:21 [PATCH] memory: renesas-rpc-if: Add missing static keyword Biju Das
2025-05-07 17:12 ` Geert Uytterhoeven
2025-05-08 8:57 ` Krzysztof Kozlowski
2025-05-08 9:05 ` Biju Das
2025-05-08 9:10 ` Krzysztof Kozlowski [this message]
2025-05-08 18:13 ` Biju Das
2025-05-08 9:25 ` Krzysztof Kozlowski
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=ff5f4f3c-75b8-46a8-83e2-b1d1533371fd@kernel.org \
--to=krzk@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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.