From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Akhil Goyal <gakhil@marvell.com>
Subject: |WARNING| pw111106 [PATCH v6 1/7] app/test: add unit cases for inline IPsec offload
Date: Fri, 13 May 2022 09:33:45 +0200 (CEST) [thread overview]
Message-ID: <20220513073345.B739F1242EF@dpdk.org> (raw)
In-Reply-To: <20220513073201.2320812-2-gakhil@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/111106
_coding style issues_
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#179: FILE: app/test/test_security_inline_proto.c:44:
+extern struct ipsec_test_data pkt_aes_128_gcm;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#180: FILE: app/test/test_security_inline_proto.c:45:
+extern struct ipsec_test_data pkt_aes_192_gcm;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#181: FILE: app/test/test_security_inline_proto.c:46:
+extern struct ipsec_test_data pkt_aes_256_gcm;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#182: FILE: app/test/test_security_inline_proto.c:47:
+extern struct ipsec_test_data pkt_aes_128_gcm_frag;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#183: FILE: app/test/test_security_inline_proto.c:48:
+extern struct ipsec_test_data pkt_aes_128_cbc_null;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#184: FILE: app/test/test_security_inline_proto.c:49:
+extern struct ipsec_test_data pkt_null_aes_xcbc;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#185: FILE: app/test/test_security_inline_proto.c:50:
+extern struct ipsec_test_data pkt_aes_128_cbc_hmac_sha384;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#186: FILE: app/test/test_security_inline_proto.c:51:
+extern struct ipsec_test_data pkt_aes_128_cbc_hmac_sha512;
total: 0 errors, 8 warnings, 933 lines checked
parent reply other threads:[~2022-05-13 7:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220513073201.2320812-2-gakhil@marvell.com>]
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=20220513073345.B739F1242EF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=gakhil@marvell.com \
--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).