From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(80155) [v2] crypto/aesni_mb: support AES-CCM-256
Date: 09 Oct 2020 22:44:35 -0700 [thread overview]
Message-ID: <fecc85$bj9qo4@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/80155
_apply issues_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: 2020-10-09 12:18:59
Reply_mail: 20201009121859.196736-1-pablo.de.lara.guarch@intel.com
DPDK git baseline:
Repo:dpdk-next-crypto, CommitID: b8617156ce0b9f697829256b0c6b6af46c9cad5d
Repo:dpdk, CommitID: 0e995cbcfc81e1d86d92dfb871ebe14ee5b8d9e4
* Repo: dpdk-next-crypto
Applying: crypto/aesni_mb: support AES-CCM-256
error: sha1 information is lacking or useless (doc/guides/cryptodevs/features/aesni_mb.ini).
error: could not build fake ancestor
Patch failed at 0001 crypto/aesni_mb: support AES-CCM-256
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
Applying: crypto/aesni_mb: support AES-CCM-256
error: sha1 information is lacking or useless (doc/guides/cryptodevs/features/aesni_mb.ini).
error: could not build fake ancestor
Patch failed at 0001 crypto/aesni_mb: support AES-CCM-256
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
next reply other threads:[~2020-10-10 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 5:44 sys_stv [this message]
2020-10-13 8:34 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='fecc85$bj9qo4@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).