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| pw98094-98098 [PATCH] [5/5] test/thash: add performance tests for the Toeplitz hash
Date: Mon,  6 Sep 2021 21:55:32 -0400 (EDT)	[thread overview]
Message-ID: <20210907015532.D2F0130551@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Monday, September 06 2021 16:03:59 
Applied on: CommitID:b344eb5d941a7522ff27b6b7b5419f68c3fea9a0
Apply patch set 98094-98098 failed:

Checking patch doc/guides/prog_guide/toeplitz_hash_lib.rst...
Checking patch doc/guides/rel_notes/release_21_11.rst...
error: while searching for:
     Also, make sure to start the actual text at the margin.
     =======================================================


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

error: patch failed: doc/guides/rel_notes/release_21_11.rst:55
Applied patch doc/guides/prog_guide/toeplitz_hash_lib.rst cleanly.
Applying patch doc/guides/rel_notes/release_21_11.rst with 1 reject...
Rejected hunk #1.
diff a/doc/guides/rel_notes/release_21_11.rst b/doc/guides/rel_notes/release_21_11.rst	(rejected hunks)
@@ -55,6 +55,10 @@ New Features
      Also, make sure to start the actual text at the margin.
      =======================================================
 
+* **Added optimized Toeplitz hash implementation.**
+
+  Added optimized Toeplitz hash implementation using Galois Fields New Instructions.
+
 
 Removed Items
 -------------

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-09-07  1:55 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=20210907015532.D2F0130551@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).