From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38292[dpdk-dev, v11, 08/10] crypto/virtio: support HMAC-SHA1
Date: 18 Apr 2018 22:32:43 -0700 [thread overview]
Message-ID: <0590c7$1ep9vq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38292
_apply issues_
Submitter: Jay Zhou <jianjay.zhou@huawei.com>
Date: 2018-04-17 09:23:24
DPDK git baseline:
Repo:dpdk-master, CommitID: e62f3a8a04768352bc78389d499be50c923bf6aa
Repo:dpdk-next-eventdev, CommitID: fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-net, CommitID: 9f44b612637c29752d1585e8d1af2e299756cd60
Repo:dpdk-next-crypto, CommitID: b1af489e6482a2247ef36418cee803e32bc84b2e
Repo:dpdk-next-virtio, CommitID: 8adbe7e4847060d091c46abcbecd3dfea8362b7a
*Repo: dpdk-master
Checking patch drivers/crypto/virtio/virtio_crypto_capabilities.h...
error: drivers/crypto/virtio/virtio_crypto_capabilities.h: No such file or directory
Checking patch drivers/crypto/virtio/virtio_cryptodev.c...
error: drivers/crypto/virtio/virtio_cryptodev.c: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch drivers/crypto/virtio/virtio_crypto_capabilities.h...
error: drivers/crypto/virtio/virtio_crypto_capabilities.h: No such file or directory
Checking patch drivers/crypto/virtio/virtio_cryptodev.c...
error: drivers/crypto/virtio/virtio_cryptodev.c: No such file or directory
*Repo: dpdk-next-net
Checking patch drivers/crypto/virtio/virtio_crypto_capabilities.h...
error: drivers/crypto/virtio/virtio_crypto_capabilities.h: No such file or directory
Checking patch drivers/crypto/virtio/virtio_cryptodev.c...
error: drivers/crypto/virtio/virtio_cryptodev.c: No such file or directory
*Repo: dpdk-next-crypto
Checking patch drivers/crypto/virtio/virtio_crypto_capabilities.h...
error: while searching for:
#define _VIRTIO_CRYPTO_CAPABILITIES_H_
#define VIRTIO_SYM_CAPABILITIES \
{ /* AES CBC */ \
.op = RTE_CRYPTO_OP_TYPE_SYMMETRIC, \
{.sym = { \
error: patch failed: drivers/crypto/virtio/virtio_crypto_capabilities.h:6
error: drivers/crypto/virtio/virtio_crypto_capabilities.h: patch does not apply
Checking patch drivers/crypto/virtio/virtio_cryptodev.c...
error: while searching for:
}
switch (auth_xform->algo) {
default:
VIRTIO_CRYPTO_SESSION_LOG_ERR(
--
*algo = VIRTIO_CRYPTO_NO_MAC;
return -1;
}
error: patch failed: drivers/crypto/virtio/virtio_cryptodev.c:1196
error: drivers/crypto/virtio/virtio_cryptodev.c: patch does not apply
*Repo: dpdk-next-virtio
Checking patch drivers/crypto/virtio/virtio_crypto_capabilities.h...
error: drivers/crypto/virtio/virtio_crypto_capabilities.h: No such file or directory
Checking patch drivers/crypto/virtio/virtio_cryptodev.c...
error: drivers/crypto/virtio/virtio_cryptodev.c: No such file or directory
DPDK STV team
next reply other threads:[~2018-04-19 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 5:32 sys_stv [this message]
2018-04-19 8:57 sys_stv
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$1ep9vq@orsmga001.jf.intel.com' \
--to=sys_stv@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).