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| pw99840-99842 [PATCH] [v2, 3/3] doc: enable protocol agnostic flow in FDIR
Date: Tue,  5 Oct 2021 18:44:25 -0400 (EDT)	[thread overview]
Message-ID: <20211005224426.0AFE36D535@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Tuesday, September 28 2021 10:18:21 
Applied on: CommitID:2700326085033fd13339a8de31f58a95d1ee9c3f
Apply patch set 99840-99842 failed:

Checking patch doc/guides/rel_notes/release_21_11.rst...
error: while searching for:
  * Added bus-level parsing of the devargs syntax.
  * Kept compatibility with the legacy syntax as parsing fallback.

* **Add new RSS offload types for IPv4/L4 checksum in RSS flow.**

  Add macros ETH_RSS_IPV4_CHKSUM and ETH_RSS_L4_CHKSUM, now IPv4 and

error: patch failed: doc/guides/rel_notes/release_21_11.rst:62
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)
@@ -62,6 +62,11 @@ New Features
   * Added bus-level parsing of the devargs syntax.
   * Kept compatibility with the legacy syntax as parsing fallback.
 
+* **Updated Intel ice driver.**
+
+  * Enabled protocol agnostic flow offloading in Flow Director based on the
+    parser library, using existing rte_flow raw API.
+
 * **Add new RSS offload types for IPv4/L4 checksum in RSS flow.**
 
   Add macros ETH_RSS_IPV4_CHKSUM and ETH_RSS_L4_CHKSUM, now IPv4 and

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-10-05 22: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=20211005224426.0AFE36D535@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).