From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw53948[v2] ipsec: support multi-segment packets
Date: 31 May 2019 04:11:49 -0700 [thread overview]
Message-ID: <ee68f5$72ofjl@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/53948
_apply issues_
Submitter: Konstantin Ananyev <konstantin.ananyev@intel.com>
Date: 2019-05-31 00:00:06
Reply_mail: 20190531000006.13918-1-konstantin.ananyev@intel.com
DPDK git baseline:
Repo:dpdk-next-crypto, CommitID: c6a53a6bcd0ae52afe0a6d58b059af577c9408b3
*Repo: dpdk-next-crypto
struct rte_esp_hdr *esph;
error: patch failed: lib/librte_ipsec/esp_inb.c:137
error: lib/librte_ipsec/esp_inb.c: patch does not apply
Checking patch lib/librte_ipsec/misc.h...
DPDK STV team
reply other threads:[~2019-05-31 11:11 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='ee68f5$72ofjl@orsmga001.jf.intel.com' \
--to=sys_stv@intel.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).