From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw135260 [PATCH v3 12/14] lib: convert to per line logging
Date: Mon, 18 Dec 2023 10:33:08 +0100 (CET) [thread overview]
Message-ID: <20231218093308.79B49121E47@dpdk.org> (raw)
In-Reply-To: <20231218092738.749604-13-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135260
_coding style issues_
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1004: FILE: lib/eal/common/eal_common_fbarray.c:758:
+ RTE_LOG_LINE(DEBUG, EAL, "%s(): couldn't remap anonymous memory: %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1013: FILE: lib/eal/common/eal_common_fbarray.c:773:
+ RTE_LOG_LINE(DEBUG, EAL, "%s(): couldn't open %s: %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#1019: FILE: lib/eal/common/eal_common_fbarray.c:778:
+ RTE_LOG_LINE(DEBUG, EAL, "%s(): couldn't lock %s: %s",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3241: FILE: lib/eal/common/hotplug_mp.c:451:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3250: FILE: lib/eal/common/hotplug_mp.c:459:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#3321: FILE: lib/eal/common/malloc_heap.c:327:
+ RTE_LOG_LINE(DEBUG, EAL, "%s(): couldn't allocate physically contiguous space",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#3332: 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'?
#3379: FILE: lib/eal/common/malloc_heap.c:1202:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't find empty memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3388: FILE: lib/eal/common/malloc_heap.c:1213:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't create fbarray backing the memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3445: FILE: lib/eal/common/malloc_heap.c:1434:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register malloc multiprocess actions");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3515: FILE: lib/eal/common/malloc_mp.c:261:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't allocate memory for request state");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3549: FILE: lib/eal/common/malloc_mp.c:348:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't send response");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3558: FILE: lib/eal/common/malloc_mp.c:379:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't send sync request");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3722: FILE: lib/eal/common/malloc_mp.c:786:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3729: FILE: lib/eal/common/malloc_mp.c:792:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3735: FILE: lib/eal/common/malloc_mp.c:797:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#3742: FILE: lib/eal/common/malloc_mp.c:803:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't register '%s' action",
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#4029: FILE: lib/eal/freebsd/eal.c:632:
+ RTE_LOG_LINE(WARNING, EAL, "Warning: ignoring unsupported flag, '%s'", OPT_IN_MEMORY);
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#4548: FILE: lib/eal/freebsd/eal_memory.c:218:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't reserve requested memory, "
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6012: FILE: lib/eal/linux/eal_memalloc.c:572:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't get fd on hugepage file");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6107: FILE: lib/eal/linux/eal_memalloc.c:751:
+ RTE_LOG_LINE(DEBUG, EAL, "couldn't unmap page");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6175: FILE: lib/eal/linux/eal_memalloc.c:1064:
+ RTE_LOG_LINE(ERR, EAL, "%s(): couldn't find suitable memseg_list",
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6202: FILE: lib/eal/linux/eal_memalloc.c:1136:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't find memseg list");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#6547: FILE: lib/eal/linux/eal_memory.c:758:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't remap '%s': %s",
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6654: 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'?
#6758: FILE: lib/eal/linux/eal_memory.c:1440:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't remap hugepage files into memseg lists");
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#6777: 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'?
#7311: FILE: lib/eal/linux/eal_vfio.c:889:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't map user memory for DMA: "
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7820: FILE: lib/eal/linux/eal_vfio.c:1868:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't map new region for DMA");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7829: FILE: lib/eal/linux/eal_vfio.c:1924:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't find previously mapped region");
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#7856: FILE: lib/eal/linux/eal_vfio.c:1981:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't unmap region for DMA");
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#8587: FILE: lib/eal/windows/eal_lcore.c:68:
+ RTE_LOG_LINE(ERR, EAL, "Cannot get group information size, error %lu", error);
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#8772: FILE: lib/eal/windows/eal_memalloc.c:414:
+ RTE_LOG_LINE(ERR, EAL, "Couldn't find memseg list");
ERROR:SPACING: space required after that ',' (ctx:VxB)
#8876: FILE: lib/eal/windows/include/rte_windows.h:52:
+ RTE_FMT_HEAD(__VA_ARGS__,), GetLastError(), \
^
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'rte_hash_create', this function's name, in a string
#9280: FILE: lib/hash/rte_cuckoo_hash.c:167:
+ RTE_LOG_LINE(ERR, HASH, "rte_hash_create has no parameters");
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'rte_hash_create', this function's name, in a string
#9289: FILE: lib/hash/rte_cuckoo_hash.c:176:
+ RTE_LOG_LINE(ERR, HASH, "rte_hash_create has invalid parameters");
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'rte_hash_create', this function's name, in a string
#9296: FILE: lib/hash/rte_cuckoo_hash.c:182:
+ RTE_LOG_LINE(ERR, HASH, "rte_hash_create: unsupported extra flags");
WARNING:EMBEDDED_FUNCTION_NAME: Prefer using '"%s...", __func__' to using 'rte_hash_create', this function's name, in a string
#9306: FILE: lib/hash/rte_cuckoo_hash.c:190:
+ RTE_LOG_LINE(ERR, HASH, "rte_hash_create: choose rw concurrency or "
total: 1 errors, 37 warnings, 14236 lines checked
parent reply other threads:[~2023-12-18 9:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231218092738.749604-13-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=20231218093308.79B49121E47@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).