From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hernan Vargas <hernan.vargas@intel.com>
Subject: |WARNING| pw141588 [PATCH v2 8/9] test/bbdev: update fft measurement output
Date: Mon, 24 Jun 2024 17:08:43 +0200 (CEST) [thread overview]
Message-ID: <20240624150843.752B0128144@dpdk.org> (raw)
In-Reply-To: <20240624150237.47169-9-hernan.vargas@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141588
_coding style issues_
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#94: FILE: app/test-bbdev/test_bbdev_perf.c:2651:
+ double estSNR, refSNR, delt, abs_delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#94: FILE: app/test-bbdev/test_bbdev_perf.c:2651:
+ double estSNR, refSNR, delt, abs_delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#117: FILE: app/test-bbdev/test_bbdev_perf.c:2674:
+ delt = refSNR - estSNR;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#118: FILE: app/test-bbdev/test_bbdev_perf.c:2675:
+ abs_delt = delt > 0 ? delt : -delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#118: FILE: app/test-bbdev/test_bbdev_perf.c:2675:
+ abs_delt = delt > 0 ? delt : -delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#118: FILE: app/test-bbdev/test_bbdev_perf.c:2675:
+ abs_delt = delt > 0 ? delt : -delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#118: FILE: app/test-bbdev/test_bbdev_perf.c:2675:
+ abs_delt = delt > 0 ? delt : -delt;
WARNING:TYPO_SPELLING: 'delt' may be misspelled - perhaps 'dealt'?
#119: FILE: app/test-bbdev/test_bbdev_perf.c:2676:
+ error_num += (abs_delt > thres_hold ? 1 : 0);
total: 0 errors, 8 warnings, 64 lines checked
parent reply other threads:[~2024-06-24 15:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240624150237.47169-9-hernan.vargas@intel.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=20240624150843.752B0128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hernan.vargas@intel.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).