automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Brandon Lo <blo@iol.unh.edu>
Subject: |WARNING| pw106611 [PATCH 4/5] examples/fips_validation: allow json file as input
Date: Thu, 27 Jan 2022 15:52:38 +0100 (CET)	[thread overview]
Message-ID: <20220127145238.52A3B120715@dpdk.org> (raw)
In-Reply-To: <20220127145142.86742-5-blo@iol.unh.edu>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106611

_coding style issues_


ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#138: FILE: examples/fips_validation/main.c:447:
+		if (use_json) json_decref(json_info.json_root);

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#171: FILE: examples/fips_validation/main.c:1259:
+	if (info.file_type != FIPS_TYPE_JSON) fips_test_write_one_case();

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#188: FILE: examples/fips_validation/main.c:1294:
+	if (info.file_type != FIPS_TYPE_JSON) fprintf(info.fp_wr, "
");

ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#257: FILE: examples/fips_validation/main.c:1951:
+	switch (info.algo) {
+		case FIPS_TEST_ALGO_AES_GCM:
[...]
+		default:

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#264: FILE: examples/fips_validation/main.c:1958:
+	if (ret < 0) return ret;

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#267: FILE: examples/fips_validation/main.c:1961:
+	if (ret < 0) return ret;

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#270: FILE: examples/fips_validation/main.c:1964:
+	if (ret < 0) return ret;

total: 7 errors, 0 warnings, 252 lines checked

           reply	other threads:[~2022-01-27 14:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220127145142.86742-5-blo@iol.unh.edu>]

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=20220127145238.52A3B120715@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=blo@iol.unh.edu \
    --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).