automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw107361-107365 [PATCH] [v7, 5/5] crypto: modify return value for asym session create
Date: Fri, 11 Feb 2022 04:49:06 -0500 (EST)	[thread overview]
Message-ID: <20220211094906.F05FEB0B3@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/107361

_apply patch failure_

Submitter: Ciara Power <ciara.power@intel.com>
Date: Friday, February 11 2022 09:29:09 
Applied on: CommitID:1d1126ad436e8c7c015fb3f67ad3af05c3b397d5
Apply patch set 107361-107365 failed:

Checking patch app/test-crypto-perf/main.c...
Checking patch app/test/test_cryptodev_asym.c...
Checking patch doc/guides/prog_guide/cryptodev_lib.rst...
Checking patch doc/guides/rel_notes/release_22_03.rst...
error: while searching for:

  The new API ``rte_event_eth_rx_adapter_event_port_get()`` was added.


Removed Items
-------------

error: patch failed: doc/guides/rel_notes/release_22_03.rst:78
Hunk #2 succeeded at 145 (offset 26 lines).
Checking patch lib/cryptodev/cryptodev_pmd.h...
Checking patch lib/cryptodev/rte_cryptodev.c...
Checking patch lib/cryptodev/rte_cryptodev.h...
Checking patch lib/cryptodev/rte_cryptodev_trace.h...
Checking patch lib/cryptodev/version.map...
Applied patch app/test-crypto-perf/main.c cleanly.
Applied patch app/test/test_cryptodev_asym.c cleanly.
Applied patch doc/guides/prog_guide/cryptodev_lib.rst cleanly.
Applying patch doc/guides/rel_notes/release_22_03.rst with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
Applied patch lib/cryptodev/cryptodev_pmd.h cleanly.
Applied patch lib/cryptodev/rte_cryptodev.c cleanly.
Applied patch lib/cryptodev/rte_cryptodev.h cleanly.
Applied patch lib/cryptodev/rte_cryptodev_trace.h cleanly.
Applied patch lib/cryptodev/version.map cleanly.
diff a/doc/guides/rel_notes/release_22_03.rst b/doc/guides/rel_notes/release_22_03.rst	(rejected hunks)
@@ -78,6 +78,10 @@ New Features
 
   The new API ``rte_event_eth_rx_adapter_event_port_get()`` was added.
 
+* **Added an API for private user data in Asymmetric crypto session.**
+
+  An API was added for getting/setting an Asymmetric crypto session's user data.
+
 
 Removed Items
 -------------
Checking patch app/test-crypto-perf/cperf_ops.c...
Checking patch app/test/test_cryptodev_asym.c...
error: app/test/test_cryptodev_asym.c: does not match index
Checking patch doc/guides/rel_notes/release_22_03.rst...
error: doc/guides/rel_notes/release_22_03.rst: does not match index
Checking patch lib/cryptodev/rte_cryptodev.c...
error: lib/cryptodev/rte_cryptodev.c: does not match index
Checking patch lib/cryptodev/rte_cryptodev.h...
error: lib/cryptodev/rte_cryptodev.h: does not match index
Checking patch lib/cryptodev/rte_cryptodev_trace.h...
error: lib/cryptodev/rte_cryptodev_trace.h: does not match index
Applied patch app/test-crypto-perf/cperf_ops.c cleanly.

https://lab.dpdk.org/results/dashboard/patchsets/21033/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-02-11  9:49 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=20220211094906.F05FEB0B3@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).