From: sys_stv@intel.com
To: alejandro.lucero@netronome.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15207 nfp: using random mac address if not a configured mac
Date: 18 Aug 2016 23:17:43 -0700 [thread overview]
Message-ID: <8dba68$v3kf5n@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15207
http://www.dpdk.org/dev/patchwork/patch/15207/
Submitter: "Alejandro.Lucero" <alejandro.lucero@netronome.com>
Date: Tue, 16 Aug 2016 16:15:28 +0100
DPDK git baseline: 0b50aa7c079ccefaef70b8e406c4e7a09eddfa63
Check patch error:
15207:
ERROR: open brace '{' following function declarations go on the next line
#45: FILE: drivers/net/nfp/nfp_net.c:620:
+static void nfp_net_read_mac(struct nfp_net_hw *hw) {
WARNING: line over 80 characters
#67: FILE: drivers/net/nfp/nfp_net.c:2419:
+ if (!is_valid_assigned_ether_addr((struct ether_addr
+*)&hw->mac_addr[0]))
total: 1 errors, 1 warnings, 48 lines checked
/home/patchWorkOrg/patches/dpdk-dev-nfp-using-random-mac-address-if-not-a-configured-mac.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-08-19 6:17 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='8dba68$v3kf5n@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=alejandro.lucero@netronome.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).