From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rosen Xu <rosen.xu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw37074 [PATCH v5 2/3] Add Intel FPGA BUS Rawdev Driver
Date: Wed, 4 Apr 2018 08:49:36 +0200 (CEST) [thread overview]
Message-ID: <20180404064936.F157E1BC3A@dpdk.org> (raw)
In-Reply-To: <1522824677-86958-3-git-send-email-rosen.xu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37074
_coding style issues_
WARNING:BAD_SIGN_OFF: email address 'Yanglong Wu <yanglong.wu@intel.com>' might be better as 'Yanglong Wu <yanglong.wu@intel.com>'
#18:
Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#272: FILE: drivers/raw/ifpga_rawdev/ifpga_rawdev.c:169:
+static int
+fpga_pr(struct rte_rawdev *raw_dev, u32 port_id, u64 *buffer, u32 size,
+ u64 *status){
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 32)
#647: FILE: drivers/raw/ifpga_rawdev/ifpga_rawdev.c:544:
+ if (rte_kvargs_process(kvlist, IFPGA_ARG_PORT,
[...]
+ IFPGA_RAWDEV_PMD_ERR("error to parse %s",
total: 1 errors, 2 warnings, 689 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-3-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=20180404064936.F157E1BC3A@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).