From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw127522-127530 [PATCH] [v2, 9/9] crypto/mlx5: enable AES-GCM capability
Date: Thu, 25 May 2023 21:10:45 -0700 (PDT) [thread overview]
Message-ID: <64703145.050a0220.f2e76.6d8eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127522
_apply patch failure_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Friday, May 26 2023 03:14:21
Applied on: CommitID:c9df59bcc9bec67783de98486879594e52bdc418
Apply patch set 127522-127530 failed:
Checking patch doc/guides/cryptodevs/mlx5.rst...
Checking patch doc/guides/rel_notes/release_23_07.rst...
error: while searching for:
* Added support for multi-packet RQ on Windows.
* Added support for CQE compression on Windows.
* Added support for enhanced multi-packet write on Windows.
* **Added flow matching of tx queue.**
error: patch failed: doc/guides/rel_notes/release_23_07.rst:29
Checking patch drivers/crypto/mlx5/mlx5_crypto.c...
Checking patch drivers/crypto/mlx5/mlx5_crypto.h...
Checking patch drivers/crypto/mlx5/mlx5_crypto_gcm.c...
Applied patch doc/guides/cryptodevs/mlx5.rst cleanly.
Applying patch doc/guides/rel_notes/release_23_07.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/crypto/mlx5/mlx5_crypto.c cleanly.
Applied patch drivers/crypto/mlx5/mlx5_crypto.h cleanly.
Applied patch drivers/crypto/mlx5/mlx5_crypto_gcm.c cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/doc/guides/rel_notes/release_23_07.rst b/doc/guides/rel_notes/release_23_07.rst (rejected hunks)
@@ -29,6 +29,7 @@ New Features
* Added support for multi-packet RQ on Windows.
* Added support for CQE compression on Windows.
* Added support for enhanced multi-packet write on Windows.
+ * Added support for AES-GCM crypto.
* **Added flow matching of tx queue.**
https://lab.dpdk.org/results/dashboard/patchsets/26403/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-05-26 4:10 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=64703145.050a0220.f2e76.6d8eSMTPIN_ADDED_MISSING@mx.google.com \
--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).