automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw71457 [PATCH 01/27] eventdev: dlb upstream prerequisites
Date: Fri, 12 Jun 2020 23:26:51 +0200 (CEST)	[thread overview]
Message-ID: <20200612212651.C467E1C1C6@dpdk.org> (raw)
In-Reply-To: <20200612212434.6852-2-timothy.mcdaniel@intel.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#85: 
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'?
#103: 
is assiged to one bit, and a port-is-single-link-only  attribute is

ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream
#147: 
Change-Id: I4cf00015296e2b3feca9886895765554730594be

ERROR:CODE_INDENT: code indent should use tabs where possible
#593: 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
#593: FILE: lib/librte_eal/x86/rte_cpuflags.c:140:
+        FEAT_DEF(UMWAIT, 0x00000007, 0, RTE_REG_ECX, 5)$

total: 2 errors, 3 warnings, 549 lines checked
Warning in /lib/librte_eventdev/rte_eventdev_pmd_pci.h:
Using rte_panic/rte_exit

           reply	other threads:[~2020-06-12 21:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200612212434.6852-2-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=20200612212651.C467E1C1C6@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).