From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Green <andy@warmcat.com>
Subject: [dpdk-test-report] |WARNING| pw39954 [PATCH v3 1/4] net/bnx2x: do not cast function pointers as a policy
Date: Mon, 14 May 2018 07:05:35 +0200 (CEST) [thread overview]
Message-ID: <20180514050535.1B2171BAC7@dpdk.org> (raw)
In-Reply-To: <152627426857.53058.13797630196021627334.stgit@localhost.localdomain>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39954
_coding style issues_
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#129: FILE: drivers/net/bnx2x/elink.c:5758:
+static uint8_t elink_format_ver(uint32_t num, uint8_t * str,
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#130: FILE: drivers/net/bnx2x/elink.c:5759:
+ uint16_t * len)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#141: FILE: drivers/net/bnx2x/elink.c:5798:
+ uint8_t * str, uint16_t * len)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#141: FILE: drivers/net/bnx2x/elink.c:5798:
+ uint8_t * str, uint16_t * len)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#257: FILE: drivers/net/bnx2x/elink.c:9824:
+static uint8_t elink_848xx_format_ver(uint32_t raw_ver, uint8_t * str,
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#293: FILE: drivers/net/bnx2x/elink.c:10619:
+static uint8_t elink_7101_format_ver(uint32_t spirom_ver, uint8_t * str,
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#294: FILE: drivers/net/bnx2x/elink.c:10620:
+ uint16_t * len)
total: 7 errors, 0 warnings, 0 checks, 570 lines checked
parent reply other threads:[~2018-05-14 5:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <152627426857.53058.13797630196021627334.stgit@localhost.localdomain>]
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=20180514050535.1B2171BAC7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andy@warmcat.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).