automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Xueming Li <xuemingl@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw94687 [PATCH v5 2/2] bus/auxiliary: introduce auxiliary bus
Date: Wed, 23 Jun 2021 02:07:01 +0200 (CEST)	[thread overview]
Message-ID: <20210623000701.F0BC0122E3A@dpdk.org> (raw)
In-Reply-To: <20210623000349.631468-2-xuemingl@nvidia.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'classs' may be misspelled - perhaps 'class'?
#128: 
  -a bus=auxiliary,name=<name>,,/class=<classs>,,/driver=<driver>,,

ERROR:SPACING: space required after that ',' (ctx:VxB)
#871: FILE: drivers/bus/auxiliary/private.h:18:
+		RTE_FMT("auxiliary bus: " RTE_FMT_HEAD(__VA_ARGS__,) "
", \
 		                                                  ^

ERROR:SPACING: space required after that ',' (ctx:VxB)
#872: FILE: drivers/bus/auxiliary/private.h:19:
+			RTE_FMT_TAIL(__VA_ARGS__,)))
 			                        ^

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#1112: FILE: drivers/bus/auxiliary/rte_bus_auxiliary.h:178:
+#define RTE_PMD_REGISTER_AUXILIARY(nm, auxiliary_drv)		\
+	RTE_INIT(auxiliaryinitfn_ ##nm)				\
+	{							\
+		(auxiliary_drv).driver.name = RTE_STR(nm);	\
+		rte_auxiliary_register(&(auxiliary_drv));	\
+	}							\
+	RTE_PMD_EXPORT_NAME(nm, __COUNTER__)

total: 3 errors, 1 warnings, 941 lines checked
--- a/doc/guides/rel_notes/release_21_08.rst
+++ b/doc/guides/rel_notes/release_21_08.rst

           reply	other threads:[~2021-06-23  0:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210623000349.631468-2-xuemingl@nvidia.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=20210623000701.F0BC0122E3A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.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).