From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoobj@marvell.com>
Subject: |WARNING| pw114813 [PATCH 1/1] app/test-security-perf: add security perf app
Date: Thu, 11 Aug 2022 06:01:06 +0200 (CEST) [thread overview]
Message-ID: <20220811040106.93450120775@dpdk.org> (raw)
In-Reply-To: <20220811035933.802-2-anoobj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/114813
_coding style issues_
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#479: FILE: app/test-security-perf/test_security_perf.c:327:
+ uint64_t tsc_start, tsc_mid, tsc_end, tsc_setup_dur, tsc_destroy_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#479: FILE: app/test-security-perf/test_security_perf.c:327:
+ uint64_t tsc_start, tsc_mid, tsc_end, tsc_setup_dur, tsc_destroy_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#536: FILE: app/test-security-perf/test_security_perf.c:384:
+ tsc_setup_dur = tsc_mid - tsc_start;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#537: FILE: app/test-security-perf/test_security_perf.c:385:
+ tsc_destroy_dur = tsc_end - tsc_mid;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#539: FILE: app/test-security-perf/test_security_perf.c:387:
+ setup_ms = tsc_setup_dur * 1000 / rte_get_tsc_hz();
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#540: FILE: app/test-security-perf/test_security_perf.c:388:
+ destroy_ms = tsc_destroy_dur * 1000 / rte_get_tsc_hz();
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#542: FILE: app/test-security-perf/test_security_perf.c:390:
+ setup_rate = (double)nb_sessions * rte_get_tsc_hz() / tsc_setup_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#543: FILE: app/test-security-perf/test_security_perf.c:391:
+ destroy_rate = (double)nb_sessions * rte_get_tsc_hz() / tsc_destroy_dur;
total: 0 errors, 8 warnings, 640 lines checked
next parent reply other threads:[~2022-08-11 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220811035933.802-2-anoobj@marvell.com>
2022-08-11 4:01 ` checkpatch [this message]
2022-08-11 5:19 ` |FAILURE| " 0-day Robot
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=20220811040106.93450120775@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anoobj@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).