From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Ruud.Derwig@synopsys.com, manjunath.hadli@vayavyalabs.com,
adityak@vayavyalabs.com, Shweta Raikar <shwetar@vayavyalabs.com>
Subject: Re: [PATCH v3 2/6] Add SPAcc Skcipher support
Date: Tue, 3 Jun 2025 14:07:24 +0200 [thread overview]
Message-ID: <ba13c2f1-9b08-4ba7-8093-d55c16143cb2@kernel.org> (raw)
In-Reply-To: <CALxtO0kitR0MnjzPwVT8nsuYThTRX+fbyOH9i2z1KKnCPg1dqg@mail.gmail.com>
On 03/06/2025 14:02, Pavitrakumar Managutte wrote:
>> 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.
>>
Confirm that you understood this. You sent us code with obvious flaws
which would be found with tools. It's a proof you did not run these
static tools. It's not the job of community reviewers to replace the
tools. Using us instead of tools is... well, a mistake but if you think
about our limited time then kind of close to inappropriate request. So
did you understand the need of using tools BEFORE you post it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-03 12:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 5:32 [PATCH v3 0/6] Add SPAcc Crypto Driver Pavitrakumar Managutte
2025-06-02 5:32 ` [PATCH v3 1/6] dt-bindings: crypto: Document support for SPAcc Pavitrakumar Managutte
2025-06-02 5:58 ` Krzysztof Kozlowski
2025-06-03 11:45 ` Pavitrakumar Managutte
2025-06-03 12:04 ` Krzysztof Kozlowski
2025-06-04 12:20 ` Pavitrakumar Managutte
2025-06-04 14:07 ` Krzysztof Kozlowski
2025-06-06 11:02 ` Pavitrakumar Managutte
2025-06-06 11:25 ` Krzysztof Kozlowski
2025-06-06 12:58 ` Pavitrakumar Managutte
2025-06-06 13:04 ` Krzysztof Kozlowski
2025-06-24 7:49 ` Pavitrakumar Managutte
2025-06-02 6:22 ` Krzysztof Kozlowski
2025-06-02 7:16 ` Ruud Derwig
2025-06-02 5:32 ` [PATCH v3 2/6] Add SPAcc Skcipher support Pavitrakumar Managutte
2025-06-02 6:05 ` Krzysztof Kozlowski
2025-06-03 12:02 ` Pavitrakumar Managutte
2025-06-03 12:07 ` Krzysztof Kozlowski [this message]
2025-06-04 10:50 ` Pavitrakumar Managutte
2025-06-02 5:32 ` [PATCH v3 3/6] Add SPAcc AUTODETECT Support Pavitrakumar Managutte
2025-06-02 5:32 ` [PATCH v3 4/6] Add SPAcc ahash support Pavitrakumar Managutte
2025-06-02 5:32 ` [PATCH v3 5/6] Add SPAcc AEAD support Pavitrakumar Managutte
2025-06-02 5:32 ` [PATCH v3 6/6] Add SPAcc Kconfig and Makefile Pavitrakumar Managutte
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=ba13c2f1-9b08-4ba7-8093-d55c16143cb2@kernel.org \
--to=krzk@kernel.org \
--cc=Ruud.Derwig@synopsys.com \
--cc=adityak@vayavyalabs.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=pavitrakumarm@vayavyalabs.com \
--cc=robh@kernel.org \
--cc=shwetar@vayavyalabs.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