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: [dpdk-test-report] |WARNING| pw99988 [PATCH] doc/guides: update dev list with Marvell crypto PMDs
Date: Tue,  5 Oct 2021 09:44:15 -0400 (EDT)	[thread overview]
Message-ID: <20211005134415.BBB056D535@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, September 29 2021 09:54:53 
Applied on: CommitID:086d426406bd3f6fac96a15bbd871c7fe714bc2d
Apply patch set 99988 failed:

Checking patch doc/guides/tools/cryptoperf.rst...
error: while searching for:

        Set device type, where ``name`` is one of the following::

           crypto_null
           crypto_aesni_mb
           crypto_aesni_gcm
           crypto_openss
           crypto_qat
           crypto_snow3g
           crypto_kasumi
           crypto_zuc
           crypto_dpaa_sec
           crypto_dpaa2_sec
           crypto_armv8
           crypto_scheduler
           crypto_mvsam

* ``--optype <name>``


error: patch failed: doc/guides/tools/cryptoperf.rst:146
Applying patch doc/guides/tools/cryptoperf.rst with 1 reject...
Rejected hunk #1.
diff a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst	(rejected hunks)
@@ -146,19 +146,23 @@ The following are the application command-line options:
 
         Set device type, where ``name`` is one of the following::
 
-           crypto_null
-           crypto_aesni_mb
            crypto_aesni_gcm
+           crypto_aesni_mb
+           crypto_armv8
+           crypto_cn9k
+           crypto_cn10k
+           crypto_dpaa_sec
+           crypto_dpaa2_sec
+           crypto_kasumi
+           crypto_mvsam
+           crypto_null
+           crypto_octeontx
+           crypto_octeontx2
            crypto_openss
            crypto_qat
+           crypto_scheduler
            crypto_snow3g
-           crypto_kasumi
            crypto_zuc
-           crypto_dpaa_sec
-           crypto_dpaa2_sec
-           crypto_armv8
-           crypto_scheduler
-           crypto_mvsam
 
 * ``--optype <name>``
 

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-10-05 13:44 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=20211005134415.BBB056D535@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).