From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw117254 [PATCH] [v3, 1/1] lib/cryptodev: multi-process IPC request handler
Date: Sun, 2 Oct 2022 19:02:48 -0400 (EDT) [thread overview]
Message-ID: <20221002230248.1FCB56D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/117254
_apply patch failure_
Submitter: Kai Ji <kai.ji@intel.com>
Date: Sunday, October 02 2022 22:44:36
Applied on: CommitID:e5d0e3c759e1048c51ee85c463a4de509d382c49
Apply patch set 117254 failed:
Checking patch lib/cryptodev/cryptodev_pmd.h...
Checking patch lib/cryptodev/rte_cryptodev.c...
Hunk #2 succeeded at 948 (offset -105 lines).
Hunk #3 succeeded at 1035 (offset -109 lines).
Hunk #4 succeeded at 1305 (offset -116 lines).
Checking patch lib/cryptodev/rte_cryptodev.h...
Checking patch lib/cryptodev/version.map...
error: while searching for:
__rte_cryptodev_trace_sym_session_get_user_data;
__rte_cryptodev_trace_sym_session_set_user_data;
__rte_cryptodev_trace_count;
};
INTERNAL {
error: patch failed: lib/cryptodev/version.map:157
Applied patch lib/cryptodev/cryptodev_pmd.h cleanly.
Applied patch lib/cryptodev/rte_cryptodev.c cleanly.
Applied patch lib/cryptodev/rte_cryptodev.h cleanly.
Applying patch lib/cryptodev/version.map with 1 reject...
Rejected hunk #1.
diff a/lib/cryptodev/version.map b/lib/cryptodev/version.map (rejected hunks)
@@ -157,6 +157,8 @@ EXPERIMENTAL {
__rte_cryptodev_trace_sym_session_get_user_data;
__rte_cryptodev_trace_sym_session_set_user_data;
__rte_cryptodev_trace_count;
+ rte_cryptodev_mp_request_register;
+ rte_cryptodev_mp_request_unregister;
};
INTERNAL {
https://lab.dpdk.org/results/dashboard/patchsets/23740/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-10-02 23:02 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=20221002230248.1FCB56D509@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).