From: sys_stv@intel.com
To: yongjiex.gu@intel.com, weichunx.chen@intel.com,
huilongx.xu@intel.com, gangx.xu@intel.com, peipeix.lu@intel.com,
ferruh.yigit@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16999 net: align ethdev and eal driver names
Date: 10 Nov 2016 10:52:31 -0800 [thread overview]
Message-ID: <587443$2c7eo@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16999
http://www.dpdk.org/dev/patchwork/patch/16999/
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Thu, 10 Nov 2016 18:46:17 +0000
DPDK git baseline: a4366ade74de491f008224bc2af2c75bea68e4a9
Check patch error:
16999:
WARNING: please, no spaces at the start of a line
#43: FILE: drivers/net/null/rte_eth_null.c:556:
+ eth_dev->rte_driver = &pmd_null_drv.driver;$
WARNING: please, no spaces at the start of a line
#58: FILE: lib/librte_ether/rte_ethdev.c:262:
+ eth_dev->rte_driver = pci_drv->driver.name;$
ERROR: patch seems to be corrupt (line wrapped?)
#63: FILE: lib/librte_ether/rte_ethdev.c:1557:
rte_eth_dev_info *dev_info)
WARNING: please, no spaces at the start of a line
#68: FILE: lib/librte_ether/rte_ethdev.c:1561:
+ dev_info->driver_name = dev->rte_driver->name;$
WARNING: please, no spaces at the start of a line
#90: FILE: lib/librte_ether/rte_ethdev.h:1645:
+ struct rte_driver *rte_driver;$
ERROR: Missing Signed-off-by: line(s)
total: 2 errors, 4 warnings, 41 lines checked
/home/patchWorkOrg/patches/dpdk-dev-2-2-net-align-ethdev-and-eal-driver-names.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:
16999:
patching file drivers/net/null/rte_eth_null.c
Hunk #1 FAILED at 553.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/null/rte_eth_null.c.rej
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 259.
DPDK STV team
reply other threads:[~2016-11-10 18:52 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='587443$2c7eo@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=weichunx.chen@intel.com \
--cc=yongjiex.gu@intel.com \
/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).