From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw110559 [PATCH] [v2, 1/1] crypto/cnxk: enable 3des-cbc secure capability
Date: Fri, 6 May 2022 13:01:47 -0400 (EDT) [thread overview]
Message-ID: <20220506170147.C2C2744239@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/110559
_apply patch failure_
Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Monday, May 02 2022 08:20:58
Applied on: CommitID:28c5d600723a9bb384a4b2f79bf6af8c40950bba
Apply patch set 110559 failed:
Checking patch drivers/crypto/cnxk/cnxk_cryptodev.h...
error: while searching for:
#include "roc_cpt.h"
#define CNXK_CPT_MAX_CAPS 35
#define CNXK_SEC_CRYPTO_MAX_CAPS 12
#define CNXK_SEC_MAX_CAPS 9
#define CNXK_AE_EC_ID_MAX 8
/**
error: patch failed: drivers/crypto/cnxk/cnxk_cryptodev.h:11
Checking patch drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c...
Hunk #1 succeeded at 837 (offset -25 lines).
Hunk #2 succeeded at 1149 (offset -69 lines).
Checking patch drivers/crypto/cnxk/cnxk_ipsec.h...
Applying patch drivers/crypto/cnxk/cnxk_cryptodev.h with 1 reject...
Rejected hunk #1.
Applied patch drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c cleanly.
Applied patch drivers/crypto/cnxk/cnxk_ipsec.h cleanly.
diff a/drivers/crypto/cnxk/cnxk_cryptodev.h b/drivers/crypto/cnxk/cnxk_cryptodev.h (rejected hunks)
@@ -11,7 +11,7 @@
#include "roc_cpt.h"
#define CNXK_CPT_MAX_CAPS 35
-#define CNXK_SEC_CRYPTO_MAX_CAPS 12
+#define CNXK_SEC_CRYPTO_MAX_CAPS 13
#define CNXK_SEC_MAX_CAPS 9
#define CNXK_AE_EC_ID_MAX 8
/**
https://lab.dpdk.org/results/dashboard/patchsets/21977/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-05-06 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 17:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:39 dpdklab
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=20220506170147.C2C2744239@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).