From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hanxiao Li <li.hanxiao@zte.com.cn>
Subject: |WARNING| pw143460 [PATCH v3 8/8] zsda: add zsda crypto-session and compile file
Date: Fri, 30 Aug 2024 08:20:22 +0200 (CEST) [thread overview]
Message-ID: <20240830062022.8C726120778@dpdk.org> (raw)
In-Reply-To: <20240830060429.3039717-8-li.hanxiao@zte.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143460
_coding style issues_
ERROR:C99_COMMENTS: do not use C99 // comments
#147: FILE: drivers/crypto/zsda/zsda_sym_session.c:16:
+ // 0 1 2 3 4 5 6 7 8 9 A B
ERROR:C99_COMMENTS: do not use C99 // comments
#148: FILE: drivers/crypto/zsda/zsda_sym_session.c:17:
+ // C D E F
ERROR:C99_COMMENTS: do not use C99 // comments
#346: FILE: drivers/crypto/zsda/zsda_sym_session.c:215:
+ // The first round key is the key itself.
ERROR:C99_COMMENTS: do not use C99 // comments
#356: FILE: drivers/crypto/zsda/zsda_sym_session.c:225:
+ // All other round keys are found from the previous round keys.
ERROR:C99_COMMENTS: do not use C99 // comments
#365: FILE: drivers/crypto/zsda/zsda_sym_session.c:234:
+ // This function shifts the 4 bytes in a word to the
ERROR:C99_COMMENTS: do not use C99 // comments
#366: FILE: drivers/crypto/zsda/zsda_sym_session.c:235:
+ // left once. [a0,a1,a2,a3] becomes [a1,a2,a3,a0]
ERROR:C99_COMMENTS: do not use C99 // comments
#367: FILE: drivers/crypto/zsda/zsda_sym_session.c:236:
+ // Function RotWord()
ERROR:C99_COMMENTS: do not use C99 // comments
#377: FILE: drivers/crypto/zsda/zsda_sym_session.c:246:
+ // SubWord() is a function that takes a four-byte input
ERROR:C99_COMMENTS: do not use C99 // comments
#378: FILE: drivers/crypto/zsda/zsda_sym_session.c:247:
+ // word and applies the S-box to each of the four bytes
ERROR:C99_COMMENTS: do not use C99 // comments
#379: FILE: drivers/crypto/zsda/zsda_sym_session.c:248:
+ // to produce an output word. Function Subword()
ERROR:C99_COMMENTS: do not use C99 // comments
#392: FILE: drivers/crypto/zsda/zsda_sym_session.c:261:
+ // Function Subword()
total: 11 errors, 0 warnings, 621 lines checked
next prev parent reply other threads:[~2024-08-30 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240830060429.3039717-8-li.hanxiao@zte.com.cn>
2024-08-30 5:51 ` |SUCCESS| pw143457-143460 " qemudev
2024-08-30 5:55 ` qemudev
2024-08-30 6:20 ` checkpatch [this message]
2024-08-30 6:43 ` |FAILURE| pw143460 " 0-day Robot
2024-08-30 6:45 ` |FAILURE| pw143457-143460 [PATCH] [v3, " dpdklab
2024-08-30 6:54 ` dpdklab
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=20240830062022.8C726120778@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=li.hanxiao@zte.com.cn \
--cc=test-report@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).