From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jingjing Wu <jingjing.wu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw30629 [PATCH RFC 6/9] net/avf: enable ops for MAC VLAN offload
Date: Fri, 20 Oct 2017 10:36:42 +0200 (CEST) [thread overview]
Message-ID: <20171020083642.F24201B216@dpdk.org> (raw)
In-Reply-To: <1508488012-82704-7-git-send-email-jingjing.wu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/30629
_coding style issues_
CHECK:SPACING: spaces preferred around that '>>' (ctx:ExO)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
CHECK:SPACING: spaces preferred around that '>>' (ctx:OxO)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
CHECK:SPACING: spaces preferred around that '>>' (ctx:OxO)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
ERROR:SPACING: spaces required around that '>' (ctx:OxW)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
CHECK:SPACING: spaces preferred around that '/' (ctx:VxV)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
ERROR:SPACING: spaces required around that ':' (ctx:VxW)
#66: FILE: drivers/net/avf/avf_ethdev.c:87:
+>>>>>>> 50b4111... net/avf: enable ops for MAC VLAN offload
^
WARNING:LINE_CONTINUATIONS: Avoid unnecessary line continuations
#334: FILE: drivers/net/avf/avf_vchnl.c:768:
+ uint8_t cmd_buffer[sizeof(struct virtchnl_ether_addr_list) + \
total: 2 errors, 1 warnings, 4 checks, 336 lines checked
parent reply other threads:[~2017-10-20 8:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1508488012-82704-7-git-send-email-jingjing.wu@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=20171020083642.F24201B216@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jingjing.wu@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).