From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tim McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw72292 [PATCH 01/27] eventdev: dlb upstream prerequisites
Date: Sat, 27 Jun 2020 06:41:40 +0200 (CEST) [thread overview]
Message-ID: <20200627044140.D53881BEDF@dpdk.org> (raw)
In-Reply-To: <1593232671-5690-2-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/72292
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#89:
2) Add a new field to the rte_event_dev_config struct. This field allows the
WARNING:TYPO_SPELLING: 'assiged' may be misspelled - perhaps 'assigned'?
#107:
is assiged to one bit, and a port-is-single-link-only attribute is
ERROR:CODE_INDENT: code indent should use tabs where possible
#598: FILE: lib/librte_eal/x86/rte_cpuflags.c:140:
+ FEAT_DEF(UMWAIT, 0x00000007, 0, RTE_REG_ECX, 5)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#598: FILE: lib/librte_eal/x86/rte_cpuflags.c:140:
+ FEAT_DEF(UMWAIT, 0x00000007, 0, RTE_REG_ECX, 5)$
total: 1 errors, 3 warnings, 936 lines checked
ERROR: symbol rte_event_dev_configure is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_event_dev_info_get is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_event_port_default_conf_get is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_event_port_setup is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
Warning in /lib/librte_eventdev/rte_eventdev_pmd_pci.h:
Using rte_panic/rte_exit
parent reply other threads:[~2020-06-27 4:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1593232671-5690-2-git-send-email-timothy.mcdaniel@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=20200627044140.D53881BEDF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=timothy.mcdaniel@intel.com \
/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).