automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Amr Mokhtar <amr.mokhtar@intel.com>
Subject: [dpdk-test-report] |WARNING| pw32656 [PATCH v4 5/5] bbdev: sample app
Date: Sat, 23 Dec 2017 01:52:43 +0100 (CET)	[thread overview]
Message-ID: <20171223005243.9E2FD1B65C@dpdk.org> (raw)
In-Reply-To: <1513990331-20253-5-git-send-email-amr.mokhtar@intel.com>

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

_coding style issues_


WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#45: FILE: MAINTAINERS:280:
+F: examples/bbdev_app/

WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#48: FILE: MAINTAINERS:283:
+F: doc/guides/sample_app_ug/bbdev_app.rst

WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#305: FILE: examples/bbdev_app/main.c:57:
+#define BBDEV_ASSERT(a) do { \
+	if (!(a)) { \
+		usage(prgname); \
+		return -1; \
+	} \
+} while (0)

total: 0 errors, 3 warnings, 1325 lines checked

           reply	other threads:[~2017-12-23  0:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1513990331-20253-5-git-send-email-amr.mokhtar@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=20171223005243.9E2FD1B65C@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=amr.mokhtar@intel.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).