From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rosen Xu <rosen.xu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw37075 [PATCH v5 3/3] Add Intel FPGA OPAE Share Code
Date: Wed, 4 Apr 2018 08:49:47 +0200 (CEST) [thread overview]
Message-ID: <20180404064947.5543C1BC3B@dpdk.org> (raw)
In-Reply-To: <1522824677-86958-4-git-send-email-rosen.xu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37075
_coding style issues_
WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#8940: FILE: drivers/raw/ifpga_rawdev/base/opae_osdep.h:94:
+#define BUG() pr_err("BUG at %s:%d", __func__, __LINE__)
WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#8946: FILE: drivers/raw/ifpga_rawdev/base/opae_osdep.h:100:
+#define BUG_ON(x) ASSERT(!(x))
WARNING:SINGLE_STATEMENT_DO_WHILE_MACRO: Single statement macros should not use a do {} while (0) loop
#9002: FILE: drivers/raw/ifpga_rawdev/base/osdep_raw/osdep_generic.h:35:
+#define compiler_barrier() do { \
+ asm volatile ("" : : : "memory"); \
+} while (0)
total: 0 errors, 3 warnings, 8919 lines checked
parent reply other threads:[~2018-04-04 6:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1522824677-86958-4-git-send-email-rosen.xu@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=20180404064947.5543C1BC3B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rosen.xu@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).