From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36288[dpdk-dev] doc: announce ethdev CRC strip flag deprecation
Date: 10 May 2018 00:58:22 -0700 [thread overview]
Message-ID: <0590c7$1k584b@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3288 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36288
_apply issues_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: 2018-03-20 11:26:31
DPDK git baseline:
Repo:dpdk-master, CommitID: 8ea41438832a360aed2b7ba49fb75e310a2ff1dc
Repo:dpdk-next-eventdev, CommitID: 640b0d1e510e111694c25145466f37867453837f
Repo:dpdk-next-net, CommitID: 774c1892c434dba09998ccc76b956feb72224571
Repo:dpdk-next-crypto, CommitID: 728ca9b0d5abea82cd01dee6645456a9d56215f7
Repo:dpdk-next-virtio, CommitID: 037c0996bc927342f157426739e0cb63f2db8689
*Repo: dpdk-master
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
successful. This modification will only impact the PMDs, not the
applications.
* i40e: The default flexible payload configuration which extracts the first 16
bytes of the payload for RSS will be deprecated starting from 18.02. If
required the previous behavior can be configured using existing flow
error: patch failed: doc/guides/rel_notes/deprecation.rst:147
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
successful. This modification will only impact the PMDs, not the
applications.
* i40e: The default flexible payload configuration which extracts the first 16
bytes of the payload for RSS will be deprecated starting from 18.02. If
required the previous behavior can be configured using existing flow
error: patch failed: doc/guides/rel_notes/deprecation.rst:147
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
*Repo: dpdk-next-net
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
successful. This modification will only impact the PMDs, not the
applications.
* i40e: The default flexible payload configuration which extracts the first 16
bytes of the payload for RSS will be deprecated starting from 18.02. If
required the previous behavior can be configured using existing flow
error: patch failed: doc/guides/rel_notes/deprecation.rst:147
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
*Repo: dpdk-next-crypto
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
successful. This modification will only impact the PMDs, not the
applications.
* i40e: The default flexible payload configuration which extracts the first 16
bytes of the payload for RSS will be deprecated starting from 18.02. If
required the previous behavior can be configured using existing flow
error: patch failed: doc/guides/rel_notes/deprecation.rst:147
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
*Repo: dpdk-next-virtio
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
successful. This modification will only impact the PMDs, not the
applications.
* i40e: The default flexible payload configuration which extracts the first 16
bytes of the payload for RSS will be deprecated starting from 18.02. If
required the previous behavior can be configured using existing flow
error: patch failed: doc/guides/rel_notes/deprecation.rst:147
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
DPDK STV team
reply other threads:[~2018-05-10 7:58 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='0590c7$1k584b@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@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).