From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoobj@marvell.com>
Subject: |WARNING| pw118945 [PATCH v2] app/test-security-perf: add security perf app
Date: Fri, 21 Oct 2022 18:38:59 +0200 (CEST) [thread overview]
Message-ID: <20221021163859.1BE9F120778@dpdk.org> (raw)
In-Reply-To: <20221021163816.175-1-anoobj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/118945
_coding style issues_
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#506: FILE: app/test-security-perf/test_security_perf.c:342:
+ uint64_t tsc_start, tsc_mid, tsc_end, tsc_setup_dur, tsc_destroy_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#506: FILE: app/test-security-perf/test_security_perf.c:342:
+ uint64_t tsc_start, tsc_mid, tsc_end, tsc_setup_dur, tsc_destroy_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#561: FILE: app/test-security-perf/test_security_perf.c:397:
+ tsc_setup_dur = tsc_mid - tsc_start;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#562: FILE: app/test-security-perf/test_security_perf.c:398:
+ tsc_destroy_dur = tsc_end - tsc_mid;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#564: FILE: app/test-security-perf/test_security_perf.c:400:
+ setup_ms = tsc_setup_dur * 1000 / rte_get_tsc_hz();
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#565: FILE: app/test-security-perf/test_security_perf.c:401:
+ destroy_ms = tsc_destroy_dur * 1000 / rte_get_tsc_hz();
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#567: FILE: app/test-security-perf/test_security_perf.c:403:
+ setup_rate = (double)nb_sessions * rte_get_tsc_hz() / tsc_setup_dur;
WARNING:TYPO_SPELLING: 'dur' may be misspelled - perhaps 'due'?
#568: FILE: app/test-security-perf/test_security_perf.c:404:
+ destroy_rate = (double)nb_sessions * rte_get_tsc_hz() / tsc_destroy_dur;
total: 0 errors, 8 warnings, 673 lines checked
parent reply other threads:[~2022-10-21 16:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221021163816.175-1-anoobj@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=20221021163859.1BE9F120778@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).