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,
thomas.monjalon@6wind.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16956 ethdev: rename library for consistency
Date: 06 Nov 2016 10:54:39 -0800 [thread overview]
Message-ID: <587443$a1up@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16956
http://www.dpdk.org/dev/patchwork/patch/16956/
Submitter: Thomas Monjalon <thomas.monjalon@6wind.com>
Date: Sun, 6 Nov 2016 19:21:02 +0100
DPDK git baseline: 47ecf3a566f44b1fdd5b5c03e8ded3c184af864a
Check patch:Success
patch file error:
16956:
patching file doc/guides/rel_notes/deprecation.rst
patching file doc/guides/rel_notes/release_16_11.rst
Hunk #1 FAILED at 258.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/rel_notes/release_16_11.rst.rej
patching file lib/librte_ether/Makefile
patching file mk/rte.app.mk
patching file mk/rte.lib.mk
DPDK STV team
reply other threads:[~2016-11-06 18:54 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$a1up@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--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).