automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw87881 [RFC] pflock: add implementation of phase-fair locks
Date: Tue, 16 Feb 2021 10:37:20 +0100 (CET)	[thread overview]
Message-ID: <20210216093720.953F4C906@dpdk.org> (raw)
In-Reply-To: <20210212013838.312623-1-sthemmin@microsoft.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#465: FILE: lib/librte_eal/include/generic/rte_pflock.h:60:
+#define RTE_PFLOCK_PRES  0x2		/* Writer present bit. */

ERROR:TRAILING_WHITESPACE: trailing whitespace
#570: FILE: lib/librte_eal/include/generic/rte_pflock.h:165:
+^I$

WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#599: FILE: lib/librte_eal/include/generic/rte_pflock.h:194:
+				    (ticket & RTE_PFLOCK_PHID) | RTE_PFLOCK_PRES,

ERROR:TRAILING_WHITESPACE: trailing whitespace
#645: FILE: lib/librte_eal/include/generic/rte_pflock.h:240:
+^I$

ERROR:TRAILING_WHITESPACE: trailing whitespace
#657: FILE: lib/librte_eal/include/generic/rte_pflock.h:252:
+^I^I$

WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#665: FILE: lib/librte_eal/include/generic/rte_pflock.h:260:
+				 (ticket & RTE_PFLOCK_PHID) | RTE_PFLOCK_PRES,

WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Stephen Hemminger <stephen@networkplumber.org>' != 'Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>'

total: 3 errors, 4 warnings, 583 lines checked

           reply	other threads:[~2021-02-16  9:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210212013838.312623-1-sthemmin@microsoft.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=20210216093720.953F4C906@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).