From: sys_stv@intel.com
To: david.marchand@6wind.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw12140-12152 e1000: move pci device ids to driver
Date: 20 Apr 2016 20:08:44 -0700 [thread overview]
Message-ID: <acb6cf$smialo@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 12140-12152
http://www.dpdk.org/dev/patchwork/patch/12152/
Submitter: David Marchand <david.marchand@6wind.com>
Date: Wed, 20 Apr 2016 14:43:44 +0200
DPDK git baseline: 7d619406f31ddf115714b32778c33f6dc0ead470
Check patch error:
12151:
ERROR: Macros with multiple statements should be enclosed in a do - while loop
#77: FILE: lib/librte_eal/common/include/rte_pci.h:509:
+#define RTE_EAL_PCI_DRIVER_EXPORT(name, d) \ extern const typeof(d)
+*pcidriver_ ##name; \ const typeof(d) *pcidriver_ ##name = &d
total: 1 errors, 0 warnings, 40 lines checked
/home/patchWorkOrg/patches/dpdk-dev-v3-12-13-drivers-export-pci-drivers.patch has style problems, please review.
If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.
patch file error:
12151:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 5789.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej patching file drivers/net/mlx5/mlx5.c Hunk #1 FAILED at 646.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej patching file drivers/net/virtio/virtio_ethdev.c
Hunk #1 FAILED at 1211.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtio_ethdev.c.rej
patching file lib/librte_eal/common/include/rte_pci.h
Hunk #1 FAILED at 497.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_pci.h.rej
DPDK STV team
reply other threads:[~2016-04-21 3:08 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='acb6cf$smialo@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=david.marchand@6wind.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).