From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Volodymyr Fialko <vfialko@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw121577-121579 [PATCH 1/3] cryptodev: add SHAKE algorithm
Date: Thu, 5 Jan 2023 06:10:15 +0800 [thread overview]
Message-ID: <202301042210.304MAFOr3580576@localhost.localdomain> (raw)
In-Reply-To: <20230104143815.603524-2-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/121577
_apply patch failure_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Wed, 4 Jan 2023 15:38:13 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 373f4c7de8ff350548cacc3d56e788461677f2c7
Apply patch set 121577-121579 failed:
Checking patch app/test/test_cryptodev_hash_test_vectors.h...
Hunk #1 succeeded at 332 (offset -206 lines).
error: while searching for:
.test_data = &hmac_sha3_512_test_vector,
.op_mask = BLOCKCIPHER_TEST_OP_AUTH_VERIFY,
},
{
.test_descr = "CMAC Digest 12B",
.test_data = &cmac_test_vector_12,
error: patch failed: app/test/test_cryptodev_hash_test_vectors.h:853
error: app/test/test_cryptodev_hash_test_vectors.h: patch does not apply
next prev parent reply other threads:[~2023-01-04 22:21 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230104143815.603524-2-vfialko@marvell.com>
2023-01-04 14:40 ` |SUCCESS| pw121577 " checkpatch
2023-01-04 14:41 ` |WARNING| pw121577-121579 " qemudev
2023-01-04 14:41 ` qemudev
2023-01-04 14:51 ` qemudev
2023-01-04 15:00 ` qemudev
2023-01-04 15:00 ` qemudev
2023-01-04 15:16 ` qemudev
2023-01-04 15:20 ` qemudev
2023-01-04 15:30 ` qemudev
2023-01-04 15:35 ` qemudev
2023-01-04 15:35 ` qemudev
2023-01-04 15:45 ` qemudev
2023-01-04 16:30 ` qemudev
2023-01-04 16:40 ` qemudev
2023-01-04 16:50 ` qemudev
2023-01-04 16:50 ` qemudev
2023-01-04 16:55 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:00 ` qemudev
2023-01-04 17:05 ` qemudev
2023-01-04 17:05 ` qemudev
2023-01-04 17:10 ` qemudev
2023-01-04 17:10 ` qemudev
2023-01-04 17:15 ` qemudev
2023-01-04 17:20 ` qemudev
2023-01-04 17:25 ` qemudev
2023-01-04 17:25 ` qemudev
2023-01-04 17:30 ` qemudev
2023-01-04 17:35 ` qemudev
2023-01-04 17:35 ` qemudev
2023-01-04 17:40 ` qemudev
2023-01-04 17:45 ` qemudev
2023-01-04 17:45 ` qemudev
2023-01-04 17:50 ` qemudev
2023-01-04 17:55 ` qemudev
2023-01-04 18:00 ` qemudev
2023-01-04 18:00 ` qemudev
2023-01-04 18:05 ` qemudev
2023-01-04 18:05 ` qemudev
2023-01-04 18:30 ` qemudev
2023-01-04 18:30 ` qemudev
2023-01-04 18:35 ` qemudev
2023-01-04 18:50 ` qemudev
2023-01-04 18:55 ` qemudev
2023-01-04 18:55 ` qemudev
2023-01-04 19:05 ` qemudev
2023-01-04 19:05 ` qemudev
2023-01-04 19:10 ` qemudev
2023-01-04 19:10 ` qemudev
2023-01-04 19:25 ` qemudev
2023-01-04 19:30 ` qemudev
2023-01-04 19:30 ` qemudev
2023-01-04 19:50 ` qemudev
2023-01-04 19:55 ` qemudev
2023-01-04 20:10 ` qemudev
2023-01-04 20:20 ` qemudev
2023-01-04 20:25 ` qemudev
2023-01-04 20:25 ` qemudev
2023-01-04 20:35 ` qemudev
2023-01-04 20:42 ` qemudev
2023-01-04 20:55 ` qemudev
2023-01-04 21:00 ` qemudev
2023-01-04 21:45 ` qemudev
2023-01-04 21:50 ` qemudev
2023-01-04 21:55 ` qemudev
2023-01-04 21:55 ` qemudev
2023-01-04 22:10 ` qemudev [this message]
2023-01-04 22:10 ` qemudev
2023-01-04 22:20 ` qemudev
2023-01-04 22:20 ` qemudev
2023-01-04 23:05 ` qemudev
2023-01-04 23:05 ` qemudev
2023-01-04 23:15 ` qemudev
2023-01-04 23:15 ` qemudev
2023-01-04 23:45 ` qemudev
2023-01-05 0:05 ` qemudev
2023-01-05 0:15 ` qemudev
2023-01-05 0:20 ` qemudev
2023-01-05 0:25 ` qemudev
2023-01-05 0:25 ` qemudev
2023-01-05 0:30 ` qemudev
2023-01-05 0:50 ` qemudev
2023-01-05 0:50 ` qemudev
2023-01-05 1:05 ` qemudev
2023-01-05 1:20 ` qemudev
2023-01-05 1:30 ` qemudev
2023-01-05 1:35 ` qemudev
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=202301042210.304MAFOr3580576@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=vfialko@marvell.com \
--cc=zhoumin@loongson.cn \
/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).