From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw117090-117095 [PATCH] [v3, 6/6] test/crypto: add cryptodev_uadk_autotest
Date: Wed, 28 Sep 2022 23:52:53 -0400 (EDT) [thread overview]
Message-ID: <20220929035253.1EE6E6D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2864 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/117090
_apply patch failure_
Submitter: Zhangfei Gao <zhangfei.gao@linaro.org>
Date: Thursday, September 29 2022 03:27:46
Applied on: CommitID:bbbe6c596b284909e4112ac9573b16da2137ffab
Apply patch set 117090-117095 failed:
Checking patch MAINTAINERS...
error: while searching for:
F: drivers/crypto/scheduler/
F: doc/guides/cryptodevs/scheduler.rst
Intel QuickAssist
M: Fan Zhang <roy.fan.zhang@intel.com>
F: drivers/crypto/qat/
error: patch failed: MAINTAINERS:1061
Checking patch doc/guides/cryptodevs/features/uadk.ini...
Checking patch doc/guides/cryptodevs/index.rst...
Checking patch doc/guides/cryptodevs/uadk.rst...
Checking patch drivers/crypto/meson.build...
Checking patch drivers/crypto/uadk/meson.build...
Checking patch drivers/crypto/uadk/uadk_crypto_pmd.c...
Checking patch drivers/crypto/uadk/version.map...
Applying patch MAINTAINERS with 1 reject...
Rejected hunk #1.
Applied patch doc/guides/cryptodevs/features/uadk.ini cleanly.
Applied patch doc/guides/cryptodevs/index.rst cleanly.
Applied patch doc/guides/cryptodevs/uadk.rst cleanly.
Applied patch drivers/crypto/meson.build cleanly.
Applied patch drivers/crypto/uadk/meson.build cleanly.
Applied patch drivers/crypto/uadk/uadk_crypto_pmd.c cleanly.
Applied patch drivers/crypto/uadk/version.map cleanly.
diff a/MAINTAINERS b/MAINTAINERS (rejected hunks)
@@ -1061,6 +1061,12 @@ M: Fan Zhang <roy.fan.zhang@intel.com>
F: drivers/crypto/scheduler/
F: doc/guides/cryptodevs/scheduler.rst
+HiSilicon UADK crypto
+M: Zhangfei Gao <zhangfei.gao@linaro.org>
+F: drivers/crypto/uadk/
+F: doc/guides/cryptodevs/uadk.rst
+F: doc/guides/cryptodevs/features/uadk.ini
+
Intel QuickAssist
M: Fan Zhang <roy.fan.zhang@intel.com>
F: drivers/crypto/qat/
Checking patch drivers/crypto/uadk/uadk_crypto_pmd.c...
error: drivers/crypto/uadk/uadk_crypto_pmd.c: does not exist in index
Checking patch drivers/crypto/uadk/uadk_crypto_pmd.c...
error: drivers/crypto/uadk/uadk_crypto_pmd.c: does not exist in index
Checking patch doc/guides/cryptodevs/features/uadk.ini...
error: doc/guides/cryptodevs/features/uadk.ini: does not exist in index
Checking patch doc/guides/cryptodevs/uadk.rst...
error: doc/guides/cryptodevs/uadk.rst: does not exist in index
Checking patch drivers/crypto/uadk/uadk_crypto_pmd.c...
error: drivers/crypto/uadk/uadk_crypto_pmd.c: does not exist in index
Checking patch doc/guides/cryptodevs/features/uadk.ini...
error: doc/guides/cryptodevs/features/uadk.ini: does not exist in index
Checking patch doc/guides/cryptodevs/uadk.rst...
error: doc/guides/cryptodevs/uadk.rst: does not exist in index
Checking patch drivers/crypto/uadk/uadk_crypto_pmd.c...
error: drivers/crypto/uadk/uadk_crypto_pmd.c: does not exist in index
https://lab.dpdk.org/results/dashboard/patchsets/23693/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-09-29 3:52 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=20220929035253.1EE6E6D509@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).