automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw129659 [PATCH v19 6/6] test/memarea: support dump API test
Date: Thu, 20 Jul 2023 11:32:08 +0200 (CEST)	[thread overview]
Message-ID: <20230720093208.747A312092E@dpdk.org> (raw)
In-Reply-To: <20230720092254.54157-7-fengchengwen@huawei.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#85: FILE: app/test/test_memarea.c:368:
+	uint32_t alloced_num = 0;

WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#109: FILE: app/test/test_memarea.c:392:
+	alloced_num++;

WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#112: FILE: app/test/test_memarea.c:395:
+	alloced_num++;

WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#115: FILE: app/test/test_memarea.c:398:
+	alloced_num++;

WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#120: FILE: app/test/test_memarea.c:403:
+	fprintf(stderr, "There should have %u allocated object.
", alloced_num);

total: 0 errors, 5 warnings, 64 lines checked

  parent reply	other threads:[~2023-07-20  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230720092254.54157-7-fengchengwen@huawei.com>
2023-07-20  9:19 ` |SUCCESS| pw129658-129659 " qemudev
2023-07-20  9:23 ` qemudev
2023-07-20  9:32 ` checkpatch [this message]
2023-07-20 10:18 ` |SUCCESS| pw129659 " 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=20230720093208.747A312092E@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=fengchengwen@huawei.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).