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| pw98661 [PATCH] crypto/ipsec_mb: support ZUC-256
Date: Fri, 10 Sep 2021 13:29:00 -0400 (EDT)	[thread overview]
Message-ID: <20210910172900.CF84330551@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Friday, September 10 2021 16:45:16 
Applied on: CommitID:0f9364522244febd96d395496b5ba2bde209d230
Apply patch set 98661 failed:

Checking patch doc/guides/cryptodevs/aesni_mb.rst...
Checking patch doc/guides/rel_notes/release_21_11.rst...
Checking patch drivers/crypto/ipsec_mb/pmd_aesni_mb.c...
error: drivers/crypto/ipsec_mb/pmd_aesni_mb.c: does not exist in index
Applied patch doc/guides/cryptodevs/aesni_mb.rst cleanly.
Applied patch doc/guides/rel_notes/release_21_11.rst cleanly.

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-09-10 17:29 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=20210910172900.CF84330551@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).