From: sys_stv@intel.com
To: rasesh.mody@qlogic.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15450-15505 qede/base: update base driver
Date: 02 Sep 2016 01:24:43 -0700 [thread overview]
Message-ID: <60e943$v4cid0@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15505,15450-15465
http://www.dpdk.org/dev/patchwork/patch/15453/
Submitter: Rasesh Mody <rasesh.mody@qlogic.com>
Date: Fri, 26 Aug 2016 23:26:13 -0700
DPDK git baseline: e22856313fff2db12d8e132dad446bbf74cf29a5
Check patch error:
15460:
ERROR: need consistent spacing around '*' (ctx:WxO)
#127: FILE: drivers/net/qede/base/ecore_l2.c:632:
+ void OSAL_IOMEM **pp_prod)
^
ERROR: need consistent spacing around '*' (ctx:WxO)
#254: FILE: drivers/net/qede/base/ecore_l2.c:873:
+ void OSAL_IOMEM **pp_doorbell)
^
ERROR: need consistent spacing around '*' (ctx:WxO)
#430: FILE: drivers/net/qede/base/ecore_l2_api.h:188:
+ void OSAL_IOMEM **pp_prod);
^
ERROR: need consistent spacing around '*' (ctx:WxO)
#471: FILE: drivers/net/qede/base/ecore_l2_api.h:238:
+ void OSAL_IOMEM **pp_doorbell);
^
total: 4 errors, 0 warnings, 645 lines checked
/home/patchWorkOrg/patches/dpdk-dev-12-17-qede-base-change-rx-tx-queue-start-APIs.patch has style problems, please review.
If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.
Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
ICC:16.0.2
i686-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-clang: compile pass
DPDK STV team
reply other threads:[~2016-09-02 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='60e943$v4cid0@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=rasesh.mody@qlogic.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).