From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw135413 [PATCH v5 09/13] lib: add more logging helpers
Date: Wed, 20 Dec 2023 16:42:34 +0100 (CET) [thread overview]
Message-ID: <20231220154234.02950121E42@dpdk.org> (raw)
In-Reply-To: <20231220153607.718606-10-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135413
_coding style issues_
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1051: FILE: lib/eal/common/eal_common_fbarray.c:758:
+ EAL_LOG(DEBUG, "%s(): couldn't remap anonymous memory: %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1060: FILE: lib/eal/common/eal_common_fbarray.c:773:
+ EAL_LOG(DEBUG, "%s(): couldn't open %s: %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1066: FILE: lib/eal/common/eal_common_fbarray.c:778:
+ EAL_LOG(DEBUG, "%s(): couldn't lock %s: %s",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3321: FILE: lib/eal/common/hotplug_mp.c:451:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3330: FILE: lib/eal/common/hotplug_mp.c:459:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#3401: FILE: lib/eal/common/malloc_heap.c:327:
+ EAL_LOG(DEBUG, "%s(): couldn't allocate physically contiguous space",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#3412: FILE: lib/eal/common/malloc_heap.c:356:
+ "%s(): couldn't allocate memory due to IOVA exceeding limits of current DMA mask",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3459: FILE: lib/eal/common/malloc_heap.c:1202:
+ EAL_LOG(ERR, "Couldn't find empty memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3468: FILE: lib/eal/common/malloc_heap.c:1213:
+ EAL_LOG(ERR, "Couldn't create fbarray backing the memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3525: FILE: lib/eal/common/malloc_heap.c:1434:
+ EAL_LOG(ERR, "Couldn't register malloc multiprocess actions");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3595: FILE: lib/eal/common/malloc_mp.c:261:
+ EAL_LOG(ERR, "Couldn't allocate memory for request state");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3629: FILE: lib/eal/common/malloc_mp.c:348:
+ EAL_LOG(ERR, "Couldn't send response");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3638: FILE: lib/eal/common/malloc_mp.c:379:
+ EAL_LOG(ERR, "Couldn't send sync request");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3802: FILE: lib/eal/common/malloc_mp.c:786:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3809: FILE: lib/eal/common/malloc_mp.c:792:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3815: FILE: lib/eal/common/malloc_mp.c:797:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3822: FILE: lib/eal/common/malloc_mp.c:803:
+ EAL_LOG(ERR, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#4650: FILE: lib/eal/freebsd/eal_memory.c:218:
+ EAL_LOG(ERR, "Couldn't reserve requested memory, "
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6114: FILE: lib/eal/linux/eal_memalloc.c:572:
+ EAL_LOG(ERR, "Couldn't get fd on hugepage file");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6209: FILE: lib/eal/linux/eal_memalloc.c:751:
+ EAL_LOG(DEBUG, "couldn't unmap page");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6277: FILE: lib/eal/linux/eal_memalloc.c:1064:
+ EAL_LOG(ERR, "%s(): couldn't find suitable memseg_list",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6304: FILE: lib/eal/linux/eal_memalloc.c:1136:
+ EAL_LOG(ERR, "Couldn't find memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6649: FILE: lib/eal/linux/eal_memory.c:758:
+ EAL_LOG(ERR, "Couldn't remap '%s': %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6756: FILE: lib/eal/linux/eal_memory.c:1235:
+ "%s(): couldn't allocate memory due to IOVA exceeding limits of current DMA mask.",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6860: FILE: lib/eal/linux/eal_memory.c:1440:
+ EAL_LOG(ERR, "Couldn't remap hugepage files into memseg lists");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6879: FILE: lib/eal/linux/eal_memory.c:1484:
+ "%s(): couldn't allocate memory due to IOVA exceeding limits of current DMA mask.",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7422: FILE: lib/eal/linux/eal_vfio.c:889:
+ EAL_LOG(ERR, "Couldn't map user memory for DMA: "
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7931: FILE: lib/eal/linux/eal_vfio.c:1868:
+ EAL_LOG(ERR, "Couldn't map new region for DMA");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7940: FILE: lib/eal/linux/eal_vfio.c:1924:
+ EAL_LOG(ERR, "Couldn't find previously mapped region");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7967: FILE: lib/eal/linux/eal_vfio.c:1981:
+ EAL_LOG(ERR, "Couldn't unmap region for DMA");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#8931: FILE: lib/eal/windows/eal_memalloc.c:414:
+ EAL_LOG(ERR, "Couldn't find memseg list");
total: 0 errors, 31 warnings, 14851 lines checked
parent reply other threads:[~2023-12-20 15:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231220153607.718606-10-david.marchand@redhat.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=20231220154234.02950121E42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).